You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jan 20, 2025. It is now read-only.
Copy file name to clipboardExpand all lines: docs/implementation/active.mdx
+72-72
Original file line number
Diff line number
Diff line change
@@ -10,83 +10,83 @@ slug: /implementations/active
10
10
11
11
| Section | Item | Priority Group | Details |
12
12
| --- | --- | --- | --- |
13
-
| 7. Code Quality |At least One Primary Maintainer has taken TBD Training on Secure Software Design |0|[details](/details/item-0)|
14
-
| 7. Code Quality |At least One Primary Maintainer has taken TBD Training on OWASP Top 10 or Equivalent |0|[details](/details/item-1)|
15
-
| 1. User Authentication |Multi Factor Authentication (MFA) Enforced Across the Github Organization |1|[details](/details/item-2)|
16
-
| 1. User Authentication |Multi Factor Authentication (MFA) Enforced Across the npm Organization |1|[details](/details/item-3)|
17
-
| 1. User Authentication |Multi Factor Authentication (MFA) Enforced in All Tools Wherever Techncially Feasible | 1|[details](/details/item-4)|
18
-
| 1. User Authentication | Use Multi Factor Authentication (MFA) Methods that Defend Against Impersonation when Available | 1|[details](/details/item-5)|
19
-
| 3. Service Authentication |No Secrets and Credentials in Source Code | 2|[details](/details/item-6)|
20
-
| 3. Service Authentication |Secrets are injected at runtime, such as environment variables or as a file (eg: use Github Secrets) | 2|[details](/details/item-7)|
21
-
| 7. Code Quality |All Commits are Scanned for Secrets and Credentials | 2|[details](/details/item-8)|
22
-
| 7. Code Quality | New Commits Containing Secrets or Credentials are Blocked from Merging | 2|[details](/details/item-9)|
23
-
| 1. User Authentication | Use SSH keys for developer access to source code repositories and use a passphrase | 3|[details](/details/item-10)|
24
-
| 3. Service Authentication | Publish to npm using an MFA-enabled account rather than single factor legacy or granular access tokens | 3|[details](/details/item-11)|
25
-
| 3. Service Authentication |Github Webhooks Use Secrets |3|[details](/details/item-12)|
26
-
| 2. User Account Permissions | Default Github Org Member Permissions Should Be Restricted | 4|[details](/details/item-13)|
27
-
| 2. User Account Permissions | Only Admins Should Be Able To Create Public Repositories |4|[details](/details/item-14)|
28
-
| 2. User Account Permissions |[For Projects with Two or more Admins] Do not allow Admins to Bypass Branch Protection Settings | 4|[details](/details/item-15)|
29
-
| 2. User Account Permissions | Define roles aligned to functional responsibilities|4|[details](/details/item-16)|
30
-
| 2. User Account Permissions | Define Individuals/Teams who Write Access to a Github Repo | 4|[details](/details/item-17)|
31
-
| 2. User Account Permissions |[For Projects with Two or more Owners] Have at least Two Owners Configured for Access Continuity |4|[details](/details/item-18)|
32
-
| 5. Vulnerability Management | Actively Exploited Critical Vulnerabilities Patched within 30 Days |5|[details](/details/item-19)|
33
-
| 5. Vulnerability Management | Non-Critical Exploitable Vulnerabilities Patched within 90 Days |5|[details](/details/item-20)|
34
-
| 11. Dependency Management |An automated process to identify dependencies with publicly disclosed vulnerabilities | 6|[details](/details/item-21)|
35
-
| 7. Code Quality | Use an Automated Static Code Analysis Tool (eg: ESLInt) | 6|[details](/details/item-22)|
36
-
| 7. Code Quality |Compilers/Linter Warnings Addressed in order to Merge | 6|[details](/details/item-23)|
37
-
| 7. Code Quality |All Commits are Scanned by a Static Application Security Testing Tool | 6|[details](/details/item-24)|
38
-
| 7. Code Quality |All Required Commit Status Checks must pass before Merging |6|[details](/details/item-25)|
| 4. Github Workflow Permissions |Consistent and Automated Build Process is Documented and Used | 12|[details](/details/item-44)|
58
-
| 5. Vulnerability Management |Commonly Used Older Versions Supported or Upgrade Path Provided/Documented | 12|[details](/details/item-45)|
59
-
| 8. Code Review |[For Projects with Two or more Maintainers]Document Software Architecture |12|[details](/details/item-46)|
60
-
| 9. Source Control | CI/CD steps should all be automated through a pipeline defined as code | 12|[details](/details/item-47)|
61
-
| 4. Github Workflows | Pin Actions with Access to Secrets to a FullLength Commit SHA|13|[details](/details/item-48)|
62
-
| 10. Dependency Inventory |Automated Process is Used to Monitor for and Maintain a List of Out of Date Dependencies |14|[details](/details/item-49)|
63
-
| 10. Dependency Inventory |[Freestanding Applications Only] A MachineReadable List of all Direct and Transitive Dependencies is Available for the Software | 14|[details](/details/item-50)|
64
-
| 10. Dependency Inventory |Modified dependencies are uniquely identified and distinct from origin dependency | 14|[details](/details/item-51)|
65
-
| 5. Vulnerability Management |A new release to refresh dependencies occurs at least annually | 14|[details](/details/item-52)|
13
+
| 7. Code Quality | Training on Secure Software Design |P0|[details](/details/softwareDesignTraining)|
14
+
| 7. Code Quality | Training on OWASP Top 10 or Equivalent |P0|[details](/details/owaspTop10Training)|
15
+
| 1. User Authentication |Enforce MFA in GitHub Organization(s)|P1|[details](/details/githubOrgMFA)|
16
+
| 1. User Authentication |Enforce MFA in npm Organization(s)|P1|[details](/details/npmOrgMFA)|
17
+
| 1. User Authentication |Enforce MFAin all the tools | P1|[details](/details/orgToolingMFA)|
18
+
| 1. User Authentication | Use MFA against impersonation | P1|[details](/details/MFAImpersonationDefense)|
19
+
| 3. Service Authentication |Check sensitive information | P2|[details](/details/noSensitiveInfoInRepositories)|
20
+
| 3. Service Authentication |Ensure that the secrets are injected at runtime| P2|[details](/details/injectedSecretsAtRuntime)|
21
+
| 7. Code Quality |Ensure that all the commits are scanned | P2|[details](/details/scanCommitsForSensitiveInfo)|
22
+
| 7. Code Quality |Block New Commits with Secrets or Credentials | P2|[details](/details/preventLandingSensitiveCommits)|
23
+
| 1. User Authentication | Use SSH Keys with Passphrases for Repository Access | P3|[details](/details/SSHKeysRequired)|
24
+
| 3. Service Authentication | Publish to npm Using MFA-Enabled Accounts | P3|[details](/details/npmPublicationMFA)|
25
+
| 3. Service Authentication |Secure GitHub Webhooks with Secrets |P3|[details](/details/githubWebhookSecrets)|
26
+
| 2. User Account Permissions |Restrict Default GitHub Org Member Permissions | P4|[details](/details/restrictedOrgPermissions)|
27
+
| 2. User Account Permissions |Allow Only Admins to Create Public Repositories |P4|[details](/details/adminRepoCreationOnly)|
28
+
| 2. User Account Permissions |Prevent Admins from Bypassing Branch Protection | P4|[details](/details/preventBranchProtectionBypass)|
29
+
| 2. User Account Permissions | Define Roles Aligned to Functional Responsibilities|P4|[details](/details/defineFunctionalRoles)|
30
+
| 2. User Account Permissions | Define Teams/Individuals with Write Access to Repositories | P4|[details](/details/githubWriteAccessRoles)|
31
+
| 2. User Account Permissions |Configure Two or more Ownersfor Access Continuity |P4|[details](/details/twoOrMoreOwnersForAccess)|
32
+
| 5. Vulnerability Management |Patch Actively Exploited Critical Vulnerabilities within 30 Days |P5|[details](/details/patchCriticalVulns30Days)|
33
+
| 5. Vulnerability Management |Patch Non-Critical Vulnerabilities within 90 Days |P5|[details](/details/patchNonCriticalVulns90Days)|
| 1. User Authentication |Github.com: Use a passkey (AAL2) or hardware key (AAL3) that activates using a password or biometrics | Rec 1 |[details](/details/item-53)|
74
-
| 1. User Authentication |Non-Interactive Github: Use a passkey (AAL2) or hardware key (AAL3) that activates using a password or biometrics | Rec 1 |[details](/details/item-54)|
75
-
| 1. User Authentication |All Other Contexts: Use a passkey (AAL2) or hardware key (AAL3) that activates using a password or biometrics | Rec 1 |[details](/details/item-55)|
76
-
| 4. Github Workflows |Limit changes from forks to workflows by requiring approval for all outside collaborators|Rec 2 |[details](/details/item-56)|
77
-
| 4. Github Workflows | Use a Workflow Security Scanner|Rec 2 |[details](/details/item-57)|
78
-
| 4. Github Workflows | Use a Github Runner Security Scanner|Rec 2 |[details](/details/item-58)|
79
-
| 2. User Account Permissions |Github Organization Admins Should Have Activity In The Last 6 Months |Rec 3 |[details](/details/item-59)|
80
-
| 2. User Account Permissions |Github Organization Members with Write Permissions Should Have Activity In The Last 6 Months |Rec 3 |[details](/details/item-60)|
81
-
| 9. Source Control | Require Pull Requests before Merging |Rec 4 |[details](/details/item-61)|
82
-
| 9. Source Control |Github Org Requires Commit Signoff for Web-Based Commits |Rec 4 |[details](/details/item-62)|
83
-
| 9. Source Control | Require Signed Commits |Rec 4 |[details](/details/item-63)|
84
-
| 10. Dependency Inventory |[Freestanding Applications Only] Commit a package-lock.json file with each release|Rec 5 |[details](/details/item-64)|
85
-
| 8. Code Review |[For Projects with Two or more Maintainers]Require TwoParty Review | Rec 6 |[details](/details/item-65)|
86
-
| 8. Code Review |[For Projects with Four or more Maintainers]Require Code Owners Review | Rec 6 |[details](/details/item-66)|
87
-
| 9. Source Control |[For Projects with Two or more Maintainers]Require Approved PRs for all commits to mainline branches | Rec 6 |[details](/details/item-67)|
88
-
| 2. User Account Permissions | Limit Number of Github Org Owners (ideally Fewer Than Three)|Rec 7 |[details](/details/item-68)|
89
-
| 2. User Account Permissions | Limit Number of Github Repository Admins (ideally Fewer Than Three)|Rec 7 |[details](/details/item-69)|
90
-
| 5. Vulnerability Management |Actively Exploited Critical and High Vulnerabilities Patched within 14 Days |Rec 8 |[details](/details/item-70)|
91
-
| 5. Vulnerability Management | Non-Critical Expoitable Vulnerabilities Patched within 60 Days |Rec 8 |[details](/details/item-71)|
73
+
| 1. User Authentication | Use AAL2/3 Passkeys for GitHub Access | R1 |[details](/details/useHwKeyGithubAccess)|
74
+
| 1. User Authentication | Use AAL2/3 Passkeys for Non-Interactive GitHub Access | R1 |[details](/details/useHwKeyGithubNonInteractive)|
75
+
| 1. User Authentication | Use AAL2/3 Passkeys in All Other Contexts | R1 |[details](/details/useHwKeyOtherContexts)|
0 commit comments