Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

feat: add transformation from OSCAL SSP to OSCAL Assessment Plan #45

Open
wants to merge 6 commits into
base: main
Choose a base branch
from
Open

feat: add transformation from OSCAL SSP to OSCAL Assessment Plan #45

wants to merge 6 commits into from

Conversation

jpower432
Copy link
Member

Description

Add a transformation for SSP to Assessment Plan using existing generation for Component Definitions

  • Adding generic implementations for ControlImplementation, ImplementationRequirements, and Statements to create ImplementationsSettings setting
  • Add a Component implementation for SSP System Component
  • Add top level SSP to Assessment Plan

Fixes #33
Blocked by #43

How has this been tested?

  • Unit tests added

Types of changes

  • Hot fix (emergency fix and release)
  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Documentation (change which affects the documentation site)
  • Breaking change (fix or feature that would cause existing functionality to change)

Quality assurance (all should be covered).

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing tests pass locally with my changes
  • All commits are signed-off.

@jpower432
chore: add test data with example SSP
c5df815 
Signed-off-by: Jennifer Power <[email protected]>
@jpower432
feat: add generic implementation of ControlImplementation types
20e8e26 
To reuse existing Implementation parsing logic implemented for Component Definitions,
generic implementation of ControlImplementation, ImplementedRequirement, and
Statements are added.

Signed-off-by: Jennifer Power <[email protected]>
@jpower432
feat: add generic implementation as inputs for Settings creation
95a3027 
Signed-off-by: Jennifer Power <[email protected]>
@jpower432
feat: add top-level transformer for OSCAL SSP to OSCAL AP
6285eeb 
Signed-off-by: Jennifer Power <[email protected]>
@jpower432
fix: updates Assessment Platform to remove empty component array
2b7f2d0 
Assessment Platform is a required field under Assessment Assests
but component are not. This updated that field to ensure there are
no empty component lists.

Signed-off-by: Jennifer Power <[email protected]>
@jpower432 jpower432 force-pushed the feat/transform-ssp-to-ap branch from 1692cee to 2b7f2d0 Compare February 28, 2025 16:29
@jpower432 jpower432 marked this pull request as ready for review February 28, 2025 16:37
@jpower432 jpower432 mentioned this pull request Feb 28, 2025
Open
14 tasks
@jpower432
fix: updates testdata and logic to fix validation error
c7ab3b9 
Creates a NilOrEmpty function to ensure any optional and
empty slices are not set.

Signed-off-by: Jennifer Power <[email protected]>
@jpower432 jpower432 mentioned this pull request Mar 10, 2025
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

OSCAL SSP to Assessment Plan
1 participant
@jpower432