-
Notifications
You must be signed in to change notification settings - Fork 348
feat(extensions): B+C extensions framework with NIST 800-53 compliance extension #239
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.
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
Open
ClintEastman02
wants to merge
4
commits into
awslabs:main
Choose a base branch
from
harmjeff:feat/clintae-community-extensions-clean
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 3 commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
12608d7
feat(extensions): add community extensions framework and NIST 800-53 …
ClintEastman02 c3d3a6c
feat(extensions): expand NIST 800-53 controls to AC, AU, and CA families
ClintEastman02 8452bf8
feat(extensions): implement B+C framework with consolidated selection…
ClintEastman02 63438c7
docs: update README and WORKING-WITH-AIDLC for consolidated extension…
ClintEastman02 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,59 @@ | ||
| # Extensions | ||
|
|
||
| This folder is read by the AI-DLC rules loader at workflow start. Place installed extension files here — the AI will automatically detect and load them. | ||
|
|
||
| **This README file is not processed by the extensions loader.** The loader scans subdirectories only. | ||
|
|
||
| --- | ||
|
|
||
| ## Available Extensions | ||
|
|
||
| | Extension | Category | Description | | ||
| |---|---|---| | ||
| | `security/baseline/` | security | OWASP-mapped security rules | | ||
| | `testing/property-based/` | testing | Property-based testing rules | | ||
| | `compliance/nist-800-53/` | compliance | NIST 800-53 controls mapped to AWS Control Tower, Config Rules, Security Hub, and GuardDuty | | ||
|
|
||
| --- | ||
|
|
||
| ## NIST 800-53 Compliance Controls | ||
|
|
||
| **Version**: 0.2.0 | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Where does the
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. this came from the different versions I was going through when the different versions i can revert to 0.1.0 |
||
|
|
||
| Maps ~90 NIST 800-53 controls to specific AWS mechanisms. When enabled, the workflow enforces applicable controls at each stage. | ||
|
|
||
| **Coverage:** | ||
| - **AC** (Access Control): AC-3, AC-4, AC-6, AC-12, AC-17, AC-22 + enhancements | ||
| - **AU** (Audit & Accountability): AU-2, AU-3, AU-5(2), AU-6, AU-12 | ||
| - **CA** (Assessment & Monitoring): CA-3, CA-7 | ||
|
|
||
| **Control Types**: Preventive (SCP, Declarative Policy), Proactive (CF Hook), Detective (Config Rule, Security Hub) | ||
|
|
||
| **Files:** | ||
| - `compliance/nist-800-53/nist-800-53-controls.md` — Full control mappings | ||
| - `compliance/nist-800-53/nist-800-53.opt-in.md` — Opt-in metadata | ||
|
|
||
| --- | ||
|
|
||
| ## How the Loader Works | ||
|
|
||
| At workflow start, the AI scans subdirectories under `extensions/`: | ||
|
|
||
| 1. A subfolder containing a `*.opt-in.md` file is an **opt-in extension** — during Requirements Analysis, a consolidated selection menu is presented listing all available extensions for the user to choose from | ||
| 2. A subfolder with rule `.md` files but no `*.opt-in.md` is **always enforced** — its rules are loaded immediately at workflow start | ||
| 3. The `project-type/` subfolder is **excluded from this scan** — project-type extensions are loaded by Workspace Detection | ||
|
|
||
| --- | ||
|
|
||
| ## Installing Community Extensions | ||
|
|
||
| Community extensions are hosted in external repositories and listed in `community-extensions-index.yaml` at the repo root. To install one, copy its rule files into the matching category subdirectory here: | ||
|
|
||
| ```bash | ||
| mkdir -p extensions/<category>/<extension-name> | ||
| cp <source>/*.opt-in.md <source>/*-rules.md extensions/<category>/<extension-name>/ | ||
| ``` | ||
|
|
||
| Then start a new AI-DLC session to load the extension. | ||
|
|
||
| --- | ||
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there an easy way to add the
Levelfor the Maturity Lifecycle concept ?