Skip to content

Refine cross-cutting OSCAL analysis questions - #17

Draft
pjavan wants to merge 3 commits into
OSCAL-Foundation:mainfrom
pjavan:questions-cross-cutting-assessment-assets
Draft

pjavan wants to merge 3 commits into
OSCAL-Foundation:mainfrom
pjavan:questions-cross-cutting-assessment-assets

Conversation

@pjavan

@pjavan pjavan commented Sep 24, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Consolidate assessment-asset and remediation questions shared by all three approaches.
  • Clarify assessment-plan task assignment versus assessment-results attribution, and add catalog-first SSP evidence and catalog-composition questions.
  • Remove resolved or superseded questions and keep the offline bundle and question verification in sync.

Verification

  • Full offline verifier: 2709/2709 checks passed (configured virtual environment).
  • Bundle freshness, JavaScript syntax, and git diff whitespace checks passed.

claude added 2 commits October 9, 2026 19:07
Adds idservice-oscap-validation-cd.json and cos-ansible-validation-cd.json
to the component-first examples, each pairing a service component with
the validation component that checks it, as supplied on issue 16. The
components match the four separate files, which stay in place.

Each combined file gets its own document UUID so it no longer shares
bbdf7ee6-... with the separate files. The IBM example count moves to 8 in
the source lock and its pinned test, the example index is rebaselined,
and the OSCAL inventory and bundle are regenerated. BUILD-LOG records the
change and the OSCAP target-component-uuid raised with the author.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SZjPttuYrthmLrCw9aCya2
Restore the observation-to-asset and desired-state questions to the
shared section, as accepted on the issue, and hold their ids.

Rewrite the component-first party table from the approach's own account:
the mapping provider publishes framework-to-framework mappings, rule
components carry the framework tie, validation checks carry none, the
owner selects the plan's validation components, and the auditor's run
makes observations and findings. The two stakeholder checks follow, and
which-cdef-maps now asks how another framework reaches the same rules.

Cite the copy-and-tailor convention in the component-first questions,
mark question 4 answered for component-first, state the runner
convention (assessment-asset-uuid and check-ids), and print the
editorial standard in the questions intro.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SZjPttuYrthmLrCw9aCya2
@pjavan pjavan linked an issue Oct 9, 2026 that may be closed by this pull request
@pjavan
pjavan requested a review from brian-ruf October 9, 2026 19:30

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

UPDATE for Automating Technical Hardening Guidance with OSCAL

2 participants