Security

Security audits, vulnerabilities, compliance, auth, secrets, and safe automation

skills in category: 29,001
pages available: 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 browser

Browse security skills

Showing 1,345–1,368 of 29,001 skills

Container Assurance Sandbox Egress Scope Intake GateAUse when a new container sandbox network egress request needs a bounded work scope to produce a scoped intake card for the sandbox egress evidence sheet. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; only declared destinations are reachable in the test and credentials do not leak through denied paths. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, li...securityrustgoVotes: 0GitHub stars: 2
Container Assurance Sandbox Egress Scenario Sensitivity MatrixAUse when the container sandbox network egress team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the sandbox egress evidence sheet with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; only declared destinations are reachable in the test and credentials do not leak through denied paths. Use configured search, fetch, read, browser,...securityrustgoVotes: 0GitHub stars: 2
Container Assurance Sandbox Egress Recovery Readiness DrillAUse when the container sandbox network egress workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the sandbox egress evidence sheet with starting state, test, and observed outcome. Success means the dry-run or approved non-production drill meets the predeclared recovery target and leaves the baseline intact; only declared destinations are reachable in the test and credentials do not leak through denied paths. Use configured search, fetc...securityrustgoVotes: 0GitHub stars: 2
Container Assurance Sandbox Egress Exception Triage QueueAUse when the container sandbox network egress workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the sandbox egress evidence sheet with evidence, owner, and next action. Success means every exception has a severity rationale, source, owner or explicit unassigned state, and a bounded next step; only declared destinations are reachable in the test and credentials do not leak through denied paths. Use configured search, fetch, read, br...securityrustgoVotes: 0GitHub stars: 2
Container Assurance Sandbox Egress Completeness ReconciliationAUse when the container sandbox network egress workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the sandbox egress evidence sheet with matched, unmatched, and unresolved rows. Success means counts and key fields reconcile or every variance is quantified, sourced, and left unresolved for an owner; only declared destinations are reachable in the test and credentials do not leak through denied paths. Use configured search, fe...securityrustgoVotes: 0GitHub stars: 2
Container Assurance Sandbox Egress Closeout Handoff LedgerAUse when a container sandbox network egress work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the sandbox egress evidence sheet with status, evidence, owner, and retention state. Success means all deliverables, unresolved items, approvals, and next owners are recorded, and the stop reason is explicit; only declared destinations are reachable in the test and credentials do not leak through denied paths. Use configured search, fetch, read, bro...securityrustgoVotes: 0GitHub stars: 2
Container Assurance Sandbox Egress Change Impact TraceAUse when a version, rule, source, or stakeholder change may affect container sandbox network egress to produce a before/after change record and impact map for the sandbox egress evidence sheet. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; only declared destinations are reachable in the test and credentials do not leak through denied paths. Use configured search, fetch, read, browser, test, and write capabi...securityrustgoVotes: 0GitHub stars: 2
Container Assurance Sandbox Egress Approval Evidence PacketAUse when a container sandbox network egress result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the sandbox egress evidence sheet containing options, evidence, risks, and open questions. Success means the decision owner, requested decision, source evidence, alternatives, uncertainty, and consequence of no action are all visible; only declared destinations are reachable in the test and credentials do not leak through denied paths. Use configured s...securityrustgoVotes: 0GitHub stars: 2
Container Assurance Runtime Capability Approval Evidence PacketAUse when a container runtime capability drift result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the runtime privilege comparison containing options, evidence, risks, and open questions. Success means the decision owner, requested decision, source evidence, alternatives, uncertainty, and consequence of no action are all visible; the test runtime does not exceed approved privileges and deviations are owner-routed. Use configured search, fetch, re...securityrustgoVotes: 0GitHub stars: 2
Container Assurance Platform Parity Approval Evidence PacketAUse when a multi-platform image parity result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the platform manifest comparison containing options, evidence, risks, and open questions. Success means the decision owner, requested decision, source evidence, alternatives, uncertainty, and consequence of no action are all visible; each declared platform resolves to the intended artifact and differences are explained. Use configured search, fetch, read, b...securityrustgoVotes: 0GitHub stars: 2
Container Assurance Context Secret Threshold Rule CheckAUse when a container build-context secret exposure decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the build-context exclusion report showing source, units, boundary case, and outcome. Success means the rule source and effective date are verified, units and scope match, and borderline cases are flagged rather than auto-approved; test credentials and sensitive files are excluded from the context and layers. Use configured search, fetch, read,...securityrustgoVotes: 0GitHub stars: 2
Container Assurance Context Secret Source Provenance LedgerAUse when a decision about container build-context secret exposure depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the build-context exclusion report. Success means each material claim has a source, version/date, location, and confidence note; test credentials and sensitive files are excluded from the context and layers. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record ...securityrustgoVotes: 0GitHub stars: 2
Container Assurance Context Secret Scope Intake GateAUse when a new container build-context secret exposure request needs a bounded work scope to produce a scoped intake card for the build-context exclusion report. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; test credentials and sensitive files are excluded from the context and layers. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement t...securityrustgoVotes: 0GitHub stars: 2
Container Assurance Context Secret Scenario Sensitivity MatrixAUse when the container build-context secret exposure team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the build-context exclusion report with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; test credentials and sensitive files are excluded from the context and layers. Use configured search, fetch, read, browser, test, and write...securityrustgoVotes: 0GitHub stars: 2
Container Assurance Context Secret Recovery Readiness DrillAUse when the container build-context secret exposure workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the build-context exclusion report with starting state, test, and observed outcome. Success means the dry-run or approved non-production drill meets the predeclared recovery target and leaves the baseline intact; test credentials and sensitive files are excluded from the context and layers. Use configured search, fetch, read, browser...securityrustgoVotes: 0GitHub stars: 2
Container Assurance Context Secret Exception Triage QueueAUse when the container build-context secret exposure workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the build-context exclusion report with evidence, owner, and next action. Success means every exception has a severity rationale, source, owner or explicit unassigned state, and a bounded next step; test credentials and sensitive files are excluded from the context and layers. Use configured search, fetch, read, browser, test, and...securityrustgoVotes: 0GitHub stars: 2
Container Assurance Context Secret Completeness ReconciliationAUse when the container build-context secret exposure workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the build-context exclusion report with matched, unmatched, and unresolved rows. Success means counts and key fields reconcile or every variance is quantified, sourced, and left unresolved for an owner; test credentials and sensitive files are excluded from the context and layers. Use configured search, fetch, read, brows...securityrustgoVotes: 0GitHub stars: 2
Container Assurance Context Secret Closeout Handoff LedgerAUse when a container build-context secret exposure work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the build-context exclusion report with status, evidence, owner, and retention state. Success means all deliverables, unresolved items, approvals, and next owners are recorded, and the stop reason is explicit; test credentials and sensitive files are excluded from the context and layers. Use configured search, fetch, read, browser, test, and ...securityrustgoVotes: 0GitHub stars: 2
Container Assurance Context Secret Change Impact TraceAUse when a version, rule, source, or stakeholder change may affect container build-context secret exposure to produce a before/after change record and impact map for the build-context exclusion report. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; test credentials and sensitive files are excluded from the context and layers. Use configured search, fetch, read, browser, test, and write capabilities only when...securityrustgoVotes: 0GitHub stars: 2
Container Assurance Context Secret Approval Evidence PacketAUse when a container build-context secret exposure result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the build-context exclusion report containing options, evidence, risks, and open questions. Success means the decision owner, requested decision, source evidence, alternatives, uncertainty, and consequence of no action are all visible; test credentials and sensitive files are excluded from the context and layers. Use configured search, fetch, re...securityrustgoVotes: 0GitHub stars: 2
Container Assurance Build Inputs Approval Evidence PacketAUse when a container build-input provenance result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the build-input manifest review containing options, evidence, risks, and open questions. Success means the decision owner, requested decision, source evidence, alternatives, uncertainty, and consequence of no action are all visible; the manifest captures material inputs and unexplained network-fetched inputs are flagged. Use configured search, fetch, r...securityrustgoVotes: 0GitHub stars: 2
Container Assurance Base Digest Approval Evidence PacketAUse when a container base-image identity result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the base-image provenance ledger containing options, evidence, risks, and open questions. Success means the decision owner, requested decision, source evidence, alternatives, uncertainty, and consequence of no action are all visible; the tested base image is pinned and attributable without relying on a mutable tag. Use configured search, fetch, read, brow...securityrustgoVotes: 0GitHub stars: 2
Container Assurance Attestation Binding Approval Evidence PacketAUse when a container attestation subject binding result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the attestation verification worksheet containing options, evidence, risks, and open questions. Success means the decision owner, requested decision, source evidence, alternatives, uncertainty, and consequence of no action are all visible; the statement verifies against the exact artifact and expected policy, without treating signature presence al...securityrustgoVotes: 0GitHub stars: 2
Authorizedsec Web Application Defense Threat Modeling Scope And Baseline RecordAUse when the work needs a verified goal, authorized boundary, and starting state for Authorized cybersecurity testing and defense: web application defense for threat modeling. Produce a scope-and-baseline record with scope, versions, decisions, and evidence for this task-specific gate: Rank abuse cases by asset, trust boundary, impact, likelihood, and existing controls without performing out-of-scope exploitation. Success means the owner, constraints, baseline, and acceptance signal are expli...securityrustgoVotes: 0GitHub stars: 2