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,273–1,296 of 29,001 skills

Aas Secure Delivery Extension Permissions Closeout Handoff LedgerAUse when a third-party extension permission review work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the extension permission inventory 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; every granted capability has a task need and update authority is identified. Use configured search, fetch, read, browser, test, and wr...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Extension Permissions Change Impact TraceAUse when a version, rule, source, or stakeholder change may affect third-party extension permission review to produce a before/after change record and impact map for the extension permission inventory. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; every granted capability has a task need and update authority is identified. Use configured search, fetch, read, browser, test, and write capabilities only when r...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Extension Permissions Approval Evidence PacketAUse when a third-party extension permission review result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the extension permission inventory 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; every granted capability has a task need and update authority is identified. Use configured search, fetch, read...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Dependency Reachability Threshold Rule CheckAUse when a dependency vulnerability reachability triage decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the dependency reachability evidence table 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; priority reflects verified exposure rather than severity label alone. Use configured search, fetch, r...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Dependency Reachability Source Provenance LedgerAUse when a decision about dependency vulnerability reachability triage depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the dependency reachability evidence table. Success means each material claim has a source, version/date, location, and confidence note; priority reflects verified exposure rather than severity label alone. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Rec...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Dependency Reachability Scope Intake GateAUse when a new dependency vulnerability reachability triage request needs a bounded work scope to produce a scoped intake card for the dependency reachability evidence table. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; priority reflects verified exposure rather than severity label alone. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refineme...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Dependency Reachability Scenario Sensitivity MatrixAUse when the dependency vulnerability reachability triage team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the dependency reachability evidence table with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; priority reflects verified exposure rather than severity label alone. Use configured search, fetch, read, browser, test, and w...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Dependency Reachability Recovery Readiness DrillAUse when the dependency vulnerability reachability triage workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the dependency reachability evidence table 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; priority reflects verified exposure rather than severity label alone. Use configured search, fetch, read, bro...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Dependency Reachability Exception Triage QueueAUse when the dependency vulnerability reachability triage workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the dependency reachability evidence table 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; priority reflects verified exposure rather than severity label alone. Use configured search, fetch, read, browser, test,...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Dependency Reachability Completeness ReconciliationAUse when the dependency vulnerability reachability triage workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the dependency reachability evidence table 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; priority reflects verified exposure rather than severity label alone. Use configured search, fetch, read, b...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Dependency Reachability Closeout Handoff LedgerAUse when a dependency vulnerability reachability triage work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the dependency reachability evidence table 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; priority reflects verified exposure rather than severity label alone. Use configured search, fetch, read, browser, test, ...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Dependency Reachability Change Impact TraceAUse when a version, rule, source, or stakeholder change may affect dependency vulnerability reachability triage to produce a before/after change record and impact map for the dependency reachability evidence table. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; priority reflects verified exposure rather than severity label alone. Use configured search, fetch, read, browser, test, and write capabilities only ...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Dependency Reachability Approval Evidence PacketAUse when a dependency vulnerability reachability triage result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the dependency reachability evidence table 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; priority reflects verified exposure rather than severity label alone. Use configured search, fetch...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Csp Report Threshold Rule CheckAUse when a content security policy report analysis decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the CSP violation triage summary 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; genuine policy gaps are separated from expected noise without weakening enforcement. Use configured search, fetch, r...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Csp Report Source Provenance LedgerAUse when a decision about content security policy report analysis depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the CSP violation triage summary. Success means each material claim has a source, version/date, location, and confidence note; genuine policy gaps are separated from expected noise without weakening enforcement. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Rec...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Csp Report Scope Intake GateAUse when a new content security policy report analysis request needs a bounded work scope to produce a scoped intake card for the CSP violation triage summary. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; genuine policy gaps are separated from expected noise without weakening enforcement. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refineme...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Csp Report Scenario Sensitivity MatrixAUse when the content security policy report analysis team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the CSP violation triage summary with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; genuine policy gaps are separated from expected noise without weakening enforcement. Use configured search, fetch, read, browser, test, and w...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Csp Report Recovery Readiness DrillAUse when the content security policy report analysis workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the CSP violation triage summary 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; genuine policy gaps are separated from expected noise without weakening enforcement. Use configured search, fetch, read, bro...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Csp Report Exception Triage QueueAUse when the content security policy report analysis workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the CSP violation triage summary 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; genuine policy gaps are separated from expected noise without weakening enforcement. Use configured search, fetch, read, browser, test,...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Csp Report Completeness ReconciliationAUse when the content security policy report analysis workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the CSP violation triage summary 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; genuine policy gaps are separated from expected noise without weakening enforcement. Use configured search, fetch, read, b...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Csp Report Closeout Handoff LedgerAUse when a content security policy report analysis work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the CSP violation triage summary 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; genuine policy gaps are separated from expected noise without weakening enforcement. Use configured search, fetch, read, browser, test, ...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Csp Report Change Impact TraceAUse when a version, rule, source, or stakeholder change may affect content security policy report analysis to produce a before/after change record and impact map for the CSP violation triage summary. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; genuine policy gaps are separated from expected noise without weakening enforcement. Use configured search, fetch, read, browser, test, and write capabilities only ...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Csp Report Approval Evidence PacketAUse when a content security policy report analysis result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the CSP violation triage summary 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; genuine policy gaps are separated from expected noise without weakening enforcement. Use configured search, fetch...securityrustgoVotes: 0GitHub stars: 2
Linux Initramfs And Rootfs Release AuditAUse when a task involves auditing a Linux initramfs or root filesystem before release to define the target, lifecycle stage, controlling artifact, authoritative evidence, version or operating conditions, sensitivity, and approval boundary before applying the method. Separate observed facts from assumptions and model output. Verify the result with appropriate independent checks, preserve provenance, and report uncertainty and limitations. Do not perform production, financial, device-control, d...securityrustrailsVotes: 0GitHub stars: 2