All categories
Security
Security audits, vulnerabilities, compliance, auth, secrets, and safe automation
- 29,002
- 1,209
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 1,465–1,488 of 29,002 skills
- Authorizedsec Container Hardening Scoped Asset Inventory Requirements And Decision BriefUse when a request must be converted into testable constraints and an owned decision for Authorized cybersecurity testing and defense: container hardening for scoped asset inventory. Produce a reviewable requirements and decision brief with scope, versions, decisions, and evidence for this task-specific gate: Record written permission, exact host/account/data boundary, exclusions, contact, and stop window before any security test. Success means requirements have priorities, evidence, owners, ...Votes: 0GitHub stars: 2
- Authorizedsec Container Hardening Scoped Asset Inventory Option Comparison MatrixUse when several tools, designs, methods, or workflows could satisfy the same need for Authorized cybersecurity testing and defense: container hardening for scoped asset inventory. Produce an evidence-backed option-comparison matrix with scope, versions, decisions, and evidence for this task-specific gate: Record written permission, exact host/account/data boundary, exclusions, contact, and stop window before any security test. Success means options are compared on user-approved criteria with...Votes: 0GitHub stars: 2
- Authorizedsec Container Hardening Scoped Asset Inventory Failure Triage And RecoveryUse when an unexpected result needs diagnosis without widening risk or losing evidence for Authorized cybersecurity testing and defense: container hardening for scoped asset inventory. Produce a failure-triage record and reversible recovery plan with scope, versions, decisions, and evidence for this task-specific gate: Record written permission, exact host/account/data boundary, exclusions, contact, and stop window before any security test. Success means the failure is bounded by observations...Votes: 0GitHub stars: 2
- Authorizedsec Container Hardening Scoped Asset Inventory Design BlueprintUse when a solution needs a coherent structure before implementation or production for Authorized cybersecurity testing and defense: container hardening for scoped asset inventory. Produce a staged design blueprint with scope, versions, decisions, and evidence for this task-specific gate: Record written permission, exact host/account/data boundary, exclusions, contact, and stop window before any security test. Success means interfaces, dependencies, constraints, and review points are testable...Votes: 0GitHub stars: 2
- Authorizedsec Container Hardening Scoped Asset Inventory Build Configuration RunbookUse when an authorized implementation needs repeatable steps and a visible change boundary for Authorized cybersecurity testing and defense: container hardening for scoped asset inventory. Produce a bounded build or configuration runbook with scope, versions, decisions, and evidence for this task-specific gate: Record written permission, exact host/account/data boundary, exclusions, contact, and stop window before any security test. Success means the prepared result is reproducible, reviewabl...Votes: 0GitHub stars: 2
- Authorizedsec Container Hardening Remediation Validation Scope And Baseline RecordUse when the work needs a verified goal, authorized boundary, and starting state for Authorized cybersecurity testing and defense: container hardening for remediation validation. Produce a scope-and-baseline record with scope, versions, decisions, and evidence for this task-specific gate: Recheck a fix with the same approved test condition and confirm no adjacent control or functionality regressed. Success means the owner, constraints, baseline, and acceptance signal are explicit. Use permiss...Votes: 0GitHub stars: 2
- Authorizedsec Container Hardening Remediation Validation Requirements And Decision BriefUse when a request must be converted into testable constraints and an owned decision for Authorized cybersecurity testing and defense: container hardening for remediation validation. Produce a reviewable requirements and decision brief with scope, versions, decisions, and evidence for this task-specific gate: Recheck a fix with the same approved test condition and confirm no adjacent control or functionality regressed. Success means requirements have priorities, evidence, owners, and measurab...Votes: 0GitHub stars: 2
- Authorizedsec Container Hardening Remediation Validation Option Comparison MatrixUse when several tools, designs, methods, or workflows could satisfy the same need for Authorized cybersecurity testing and defense: container hardening for remediation validation. Produce an evidence-backed option-comparison matrix with scope, versions, decisions, and evidence for this task-specific gate: Recheck a fix with the same approved test condition and confirm no adjacent control or functionality regressed. Success means options are compared on user-approved criteria with uncertainty...Votes: 0GitHub stars: 2
- Authorizedsec Container Hardening Remediation Validation Failure Triage And RecoveryUse when an unexpected result needs diagnosis without widening risk or losing evidence for Authorized cybersecurity testing and defense: container hardening for remediation validation. Produce a failure-triage record and reversible recovery plan with scope, versions, decisions, and evidence for this task-specific gate: Recheck a fix with the same approved test condition and confirm no adjacent control or functionality regressed. Success means the failure is bounded by observations, one testab...Votes: 0GitHub stars: 2
- Authorizedsec Container Hardening Remediation Validation Design BlueprintUse when a solution needs a coherent structure before implementation or production for Authorized cybersecurity testing and defense: container hardening for remediation validation. Produce a staged design blueprint with scope, versions, decisions, and evidence for this task-specific gate: Recheck a fix with the same approved test condition and confirm no adjacent control or functionality regressed. Success means interfaces, dependencies, constraints, and review points are testable before buil...Votes: 0GitHub stars: 2
- Authorizedsec Container Hardening Remediation Validation Build Configuration RunbookUse when an authorized implementation needs repeatable steps and a visible change boundary for Authorized cybersecurity testing and defense: container hardening for remediation validation. Produce a bounded build or configuration runbook with scope, versions, decisions, and evidence for this task-specific gate: Recheck a fix with the same approved test condition and confirm no adjacent control or functionality regressed. Success means the prepared result is reproducible, reviewable, and withi...Votes: 0GitHub stars: 2
- Authorizedsec Container Hardening Incident Handoff Scope And Baseline RecordUse when the work needs a verified goal, authorized boundary, and starting state for Authorized cybersecurity testing and defense: container hardening for incident handoff. Produce a scope-and-baseline record with scope, versions, decisions, and evidence for this task-specific gate: Preserve a minimal evidence trail, containment state, affected owner, and escalation contact without exposing sensitive data. Success means the owner, constraints, baseline, and acceptance signal are explicit. Use...Votes: 0GitHub stars: 2
- Authorizedsec Container Hardening Incident Handoff Requirements And Decision BriefUse when a request must be converted into testable constraints and an owned decision for Authorized cybersecurity testing and defense: container hardening for incident handoff. Produce a reviewable requirements and decision brief with scope, versions, decisions, and evidence for this task-specific gate: Preserve a minimal evidence trail, containment state, affected owner, and escalation contact without exposing sensitive data. Success means requirements have priorities, evidence, owners, and ...Votes: 0GitHub stars: 2
- Authorizedsec Container Hardening Incident Handoff Option Comparison MatrixUse when several tools, designs, methods, or workflows could satisfy the same need for Authorized cybersecurity testing and defense: container hardening for incident handoff. Produce an evidence-backed option-comparison matrix with scope, versions, decisions, and evidence for this task-specific gate: Preserve a minimal evidence trail, containment state, affected owner, and escalation contact without exposing sensitive data. Success means options are compared on user-approved criteria with unc...Votes: 0GitHub stars: 2
- Authorizedsec Container Hardening Incident Handoff Failure Triage And RecoveryUse when an unexpected result needs diagnosis without widening risk or losing evidence for Authorized cybersecurity testing and defense: container hardening for incident handoff. Produce a failure-triage record and reversible recovery plan with scope, versions, decisions, and evidence for this task-specific gate: Preserve a minimal evidence trail, containment state, affected owner, and escalation contact without exposing sensitive data. Success means the failure is bounded by observations, on...Votes: 0GitHub stars: 2
- Authorizedsec Container Hardening Incident Handoff Design BlueprintUse when a solution needs a coherent structure before implementation or production for Authorized cybersecurity testing and defense: container hardening for incident handoff. Produce a staged design blueprint with scope, versions, decisions, and evidence for this task-specific gate: Preserve a minimal evidence trail, containment state, affected owner, and escalation contact without exposing sensitive data. Success means interfaces, dependencies, constraints, and review points are testable bef...Votes: 0GitHub stars: 2
- Authorizedsec Container Hardening Incident Handoff Build Configuration RunbookUse when an authorized implementation needs repeatable steps and a visible change boundary for Authorized cybersecurity testing and defense: container hardening for incident handoff. Produce a bounded build or configuration runbook with scope, versions, decisions, and evidence for this task-specific gate: Preserve a minimal evidence trail, containment state, affected owner, and escalation contact without exposing sensitive data. Success means the prepared result is reproducible, reviewable, a...Votes: 0GitHub stars: 2
- Authorizedsec Container Hardening Change Impact Security Rights And Safety ReviewUse when the workflow could affect people, systems, confidential data, intellectual property, or physical outcomes for Authorized cybersecurity testing and defense: container hardening for change impact. Produce a scoped risk-and-control review with scope, versions, decisions, and evidence for this task-specific gate: Review only the approved change diff and affected trust boundaries; do not expand into neighboring assets. Success means the review names relevant hazards, permissions, controls...Votes: 0GitHub stars: 2
- Authorizedsec Container Hardening Change Impact Scope And Baseline RecordUse when the work needs a verified goal, authorized boundary, and starting state for Authorized cybersecurity testing and defense: container hardening for change impact. Produce a scope-and-baseline record with scope, versions, decisions, and evidence for this task-specific gate: Review only the approved change diff and affected trust boundaries; do not expand into neighboring assets. Success means the owner, constraints, baseline, and acceptance signal are explicit. Use permissioned inputs, ...Votes: 0GitHub stars: 2
- Authorizedsec Container Hardening Change Impact Requirements And Decision BriefUse when a request must be converted into testable constraints and an owned decision for Authorized cybersecurity testing and defense: container hardening for change impact. Produce a reviewable requirements and decision brief with scope, versions, decisions, and evidence for this task-specific gate: Review only the approved change diff and affected trust boundaries; do not expand into neighboring assets. Success means requirements have priorities, evidence, owners, and measurable acceptance ...Votes: 0GitHub stars: 2
- Authorizedsec Container Hardening Change Impact Option Comparison MatrixUse when several tools, designs, methods, or workflows could satisfy the same need for Authorized cybersecurity testing and defense: container hardening for change impact. Produce an evidence-backed option-comparison matrix with scope, versions, decisions, and evidence for this task-specific gate: Review only the approved change diff and affected trust boundaries; do not expand into neighboring assets. Success means options are compared on user-approved criteria with uncertainty and trade-off...Votes: 0GitHub stars: 2
- Authorizedsec Container Hardening Change Impact Failure Triage And RecoveryUse when an unexpected result needs diagnosis without widening risk or losing evidence for Authorized cybersecurity testing and defense: container hardening for change impact. Produce a failure-triage record and reversible recovery plan with scope, versions, decisions, and evidence for this task-specific gate: Review only the approved change diff and affected trust boundaries; do not expand into neighboring assets. Success means the failure is bounded by observations, one testable hypothesis,...Votes: 0GitHub stars: 2
- Authorizedsec Container Hardening Change Impact Design BlueprintUse when a solution needs a coherent structure before implementation or production for Authorized cybersecurity testing and defense: container hardening for change impact. Produce a staged design blueprint with scope, versions, decisions, and evidence for this task-specific gate: Review only the approved change diff and affected trust boundaries; do not expand into neighboring assets. Success means interfaces, dependencies, constraints, and review points are testable before build. Use permiss...Votes: 0GitHub stars: 2
- Authorizedsec Container Hardening Change Impact Build Configuration RunbookUse when an authorized implementation needs repeatable steps and a visible change boundary for Authorized cybersecurity testing and defense: container hardening for change impact. Produce a bounded build or configuration runbook with scope, versions, decisions, and evidence for this task-specific gate: Review only the approved change diff and affected trust boundaries; do not expand into neighboring assets. Success means the prepared result is reproducible, reviewable, and within the approved...Votes: 0GitHub stars: 2