Skip to content

Revise compliance structure to Gemara Model #4

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

Open
eddie-knight wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Revise compliance structure to Gemara Model #4

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions GOVERNANCE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ Proposals not adhering to said principles shall not be considered for consensus.

### Follow Layer-Based Architecture

The six-layer model (Guidance, Controls, Policy, Evaluation, Enforcement, Audit) provides a clear structure for organizing compliance activities. Changes respect this architectural model and relationships between layers.
The Gemara Model provides a clear structure for organizing compliance activities. Schema and documentation changes respect this model and relationships between layers.

### Ensure Engineering-Centric Design

Expand Down Expand Up @@ -100,4 +100,4 @@ This document was adapted from the Security Baseline Governance [documentation](
[MAINTAINERS.md]: ./MAINTAINERS.md
[maintainer consensus]: #maintainer-consensus
[Sponsoring Committee]: #sponsoring-committees
[Guiding Governance Principles]: #guiding-governance-principles
[Guiding Governance Principles]: #guiding-governance-principles