All categories
Security
Security audits, vulnerabilities, compliance, auth, secrets, and safe automation
- 31,765
- 1,324
Security grades appear on each card once the skill has been scanned. Newly imported skills may briefly show without a grade until the backfill job runs.
Open in full browserBrowse security skills
Showing 22,273–22,296 of 31,765 skills
- CM 7(3) Registration ComplianceEnsure compliance with [organization-defined].Votes: 0GitHub stars: 3,518
- CM 7(2) Prevent Program ExecutionPrevent program execution in accordance with [organization-defined].Votes: 0GitHub stars: 3,518
- CM 7(1) Periodic ReviewReview the system [organization-defined] to identify unnecessary and/or nonsecure functions, ports, protocols, software, and services;Votes: 0GitHub stars: 3,518
- CM 6 Configuration SettingsEstablish and document configuration settings for components employed within the system that reflect the most restrictive mode consistent with oper...Votes: 0GitHub stars: 3,518
- CM 6(4) Conformance DemonstrationConformance DemonstrationVotes: 0GitHub stars: 3,518
- CM 6(3) Unauthorized Change DetectionUnauthorized Change DetectionVotes: 0GitHub stars: 3,518
- CM 6(2) Respond To Unauthorized ChangesTake the following actions in response to unauthorized changes to [organization-defined]: [organization-defined].Votes: 0GitHub stars: 3,518
- CM 5 Access Restrictions For ChangeDefine, document, approve, and enforce physical and logical access restrictions associated with changes to the system.Votes: 0GitHub stars: 3,518
- CM 5(6) Limit Library PrivilegesLimit privileges to change software resident within software libraries.Votes: 0GitHub stars: 3,518
- CM 5(4) Dual AuthorizationEnforce dual authorization for implementing changes to [organization-defined].Votes: 0GitHub stars: 3,518
- CM 5(3) Signed ComponentsSigned ComponentsVotes: 0GitHub stars: 3,518
- CM 5(2) Review System ChangesReview System ChangesVotes: 0GitHub stars: 3,518
- CM 4 Impact AnalysesAnalyze changes to the system to determine potential security and privacy impacts prior to change implementation.Votes: 0GitHub stars: 3,518
- CM 4(2) Verification Of ControlsAfter system changes, verify that the impacted controls are implemented correctly, operating as intended, and producing the desired outcome with regarVotes: 0GitHub stars: 3,518
- CM 4(1) Separate Test EnvironmentsAnalyze changes to the system in a separate test environment before implementation in an operational environment, looking for security and privacy impVotes: 0GitHub stars: 3,518
- CM 3 Configuration Change ControlDetermine and document the types of changes to the system that are configuration-controlled;Votes: 0GitHub stars: 3,518
- CM 3(7) Review System ChangesReview changes to the system [organization-defined] or when [organization-defined] to determine whether unauthorized changes have occurred.Votes: 0GitHub stars: 3,518
- CM 3(6) Cryptography ManagementEnsure that cryptographic mechanisms used to provide the following controls are under configuration management: [organization-defined].Votes: 0GitHub stars: 3,518
- CM 3(5) Automated Security ResponseImplement the following security responses automatically if baseline configurations are changed in an unauthorized manner: [organization-defined].Votes: 0GitHub stars: 3,518
- CM 3(3) Automated Change ImplementationImplement changes to the current system baseline and deploy the updated baseline across the installed base using [organization-defined].Votes: 0GitHub stars: 3,518
- CM 2 Baseline ConfigurationDevelop, document, and maintain under configuration control, a current baseline configuration of the system;Votes: 0GitHub stars: 3,518
- CM 2(5) Authorized SoftwareAuthorized SoftwareVotes: 0GitHub stars: 3,518
- CM 2(4) Unauthorized SoftwareUnauthorized SoftwareVotes: 0GitHub stars: 3,518
- CM 2(1) Reviews And UpdatesReviews and UpdatesVotes: 0GitHub stars: 3,518