Skip to content

feat(sctm): add technical assessment section to control view - #227

Open
kevjablonski wants to merge 4 commits into
mainfrom
feat/sctm-view-technical-assessment
Open

feat(sctm): add technical assessment section to control view#227
kevjablonski wants to merge 4 commits into
mainfrom
feat/sctm-view-technical-assessment

Conversation

@kevjablonski

Copy link
Copy Markdown
Collaborator

Summary

Adds a Technical Assessment section to the SCTM view so users can review the CCIs associated with each control and the corresponding STIG checks and implementation statuses.

Changes

Added

  • Added a Technical Assessment section to the SCTM control view.
  • Displayed all CCIs mapped to each control.
  • Displayed STIG checks mapped to the applicable CCIs.
  • Included the current status of each mapped STIG check.

Testing

  • Verified that base controls display their applicable CCIs.
  • Verified that control enhancements continue to display their applicable CCIs.
  • Verified that each STIG check displays its current status.
  • Verified that controls without applicable STIG mappings are handled correctly.

Related

- List CCIs mapped to each control
- Display STIG checks associated with applicable CCIs
- Include the status of each STIG check

Signed-off-by: Kevin Jablonski <kevjablonski@gmail.com>
@Amndeep7
Amndeep7 temporarily deployed to tir-feat-sctm-view-tech-tnzjno August 4, 2026 14:58 Inactive
Signed-off-by: Kevin Jablonski <kevjablonski@gmail.com>
@Amndeep7
Amndeep7 temporarily deployed to tir-feat-sctm-view-tech-tnzjno August 4, 2026 19:30 Inactive
Signed-off-by: Kevin Jablonski <kevjablonski@gmail.com>
@Amndeep7
Amndeep7 temporarily deployed to tir-feat-sctm-view-tech-tnzjno August 4, 2026 19:57 Inactive
Signed-off-by: Kevin Jablonski <kevjablonski@gmail.com>
@sonarqubecloud

sonarqubecloud Bot commented Aug 5, 2026

Copy link
Copy Markdown

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.

2 participants