Security

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

skills in category: 28,990
pages available: 1,208

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,177–1,200 of 28,990 skills

Aas Secure Delivery Vulnerability Response Scope Intake GateAUse when a new application vulnerability response coordination request needs a bounded work scope to produce a scoped intake card for the vulnerability response handoff. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; a responsible owner and safe next step are assigned without publishing sensitive details. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence,...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Vulnerability Response Scenario Sensitivity MatrixAUse when the application vulnerability response coordination team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the vulnerability response handoff with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; a responsible owner and safe next step are assigned without publishing sensitive details. Use configured search, fetch, read, brows...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Vulnerability Response Recovery Readiness DrillAUse when the application vulnerability response coordination workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the vulnerability response handoff 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; a responsible owner and safe next step are assigned without publishing sensitive details. Use configured search, f...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Vulnerability Response Exception Triage QueueAUse when the application vulnerability response coordination workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the vulnerability response handoff 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; a responsible owner and safe next step are assigned without publishing sensitive details. Use configured search, fetch, read,...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Vulnerability Response Completeness ReconciliationAUse when the application vulnerability response coordination workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the vulnerability response handoff 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; a responsible owner and safe next step are assigned without publishing sensitive details. Use configured search,...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Vulnerability Response Closeout Handoff LedgerAUse when a application vulnerability response coordination work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the vulnerability response handoff 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; a responsible owner and safe next step are assigned without publishing sensitive details. Use configured search, fetch, read, ...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Vulnerability Response Change Impact TraceAUse when a version, rule, source, or stakeholder change may affect application vulnerability response coordination to produce a before/after change record and impact map for the vulnerability response handoff. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; a responsible owner and safe next step are assigned without publishing sensitive details. Use configured search, fetch, read, browser, test, and write cap...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Vulnerability Response Approval Evidence PacketAUse when a application vulnerability response coordination result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the vulnerability response handoff 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; a responsible owner and safe next step are assigned without publishing sensitive details. Use configure...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Tenant Authz Threshold Rule CheckAUse when a multi-tenant authorization boundaries decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the tenant isolation test record 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; cross-tenant access is denied across direct, indirect, and asynchronous paths. Use configured search, fetch, read, bro...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Tenant Authz Source Provenance LedgerAUse when a decision about multi-tenant authorization boundaries depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the tenant isolation test record. Success means each material claim has a source, version/date, location, and confidence note; cross-tenant access is denied across direct, indirect, and asynchronous paths. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evid...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Tenant Authz Scope Intake GateAUse when a new multi-tenant authorization boundaries request needs a bounded work scope to produce a scoped intake card for the tenant isolation test record. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; cross-tenant access is denied across direct, indirect, and asynchronous paths. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to th...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Tenant Authz Scenario Sensitivity MatrixAUse when the multi-tenant authorization boundaries team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the tenant isolation test record with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; cross-tenant access is denied across direct, indirect, and asynchronous paths. Use configured search, fetch, read, browser, test, and write cap...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Tenant Authz Recovery Readiness DrillAUse when the multi-tenant authorization boundaries workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the tenant isolation test record 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; cross-tenant access is denied across direct, indirect, and asynchronous paths. Use configured search, fetch, read, browser, te...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Tenant Authz Exception Triage QueueAUse when the multi-tenant authorization boundaries workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the tenant isolation test record 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; cross-tenant access is denied across direct, indirect, and asynchronous paths. Use configured search, fetch, read, browser, test, and wri...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Tenant Authz Completeness ReconciliationAUse when the multi-tenant authorization boundaries workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the tenant isolation test record 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; cross-tenant access is denied across direct, indirect, and asynchronous paths. Use configured search, fetch, read, browser, ...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Tenant Authz Closeout Handoff LedgerAUse when a multi-tenant authorization boundaries work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the tenant isolation test record 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; cross-tenant access is denied across direct, indirect, and asynchronous paths. Use configured search, fetch, read, browser, test, and writ...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Tenant Authz Change Impact TraceAUse when a version, rule, source, or stakeholder change may affect multi-tenant authorization boundaries to produce a before/after change record and impact map for the tenant isolation test record. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; cross-tenant access is denied across direct, indirect, and asynchronous paths. Use configured search, fetch, read, browser, test, and write capabilities only when rel...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Tenant Authz Approval Evidence PacketAUse when a multi-tenant authorization boundaries result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the tenant isolation test record 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; cross-tenant access is denied across direct, indirect, and asynchronous paths. Use configured search, fetch, read, ...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Security Header Threshold Rule CheckAUse when a web response security header regression decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the response-header comparison 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; required headers appear on in-scope responses without breaking declared flows. Use configured search, fetch, read, bro...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Security Header Source Provenance LedgerAUse when a decision about web response security header regression depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the response-header comparison. Success means each material claim has a source, version/date, location, and confidence note; required headers appear on in-scope responses without breaking declared flows. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evid...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Security Header Scope Intake GateAUse when a new web response security header regression request needs a bounded work scope to produce a scoped intake card for the response-header comparison. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; required headers appear on in-scope responses without breaking declared flows. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to th...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Security Header Scenario Sensitivity MatrixAUse when the web response security header regression team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the response-header comparison with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; required headers appear on in-scope responses without breaking declared flows. Use configured search, fetch, read, browser, test, and write cap...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Security Header Recovery Readiness DrillAUse when the web response security header regression workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the response-header comparison 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; required headers appear on in-scope responses without breaking declared flows. Use configured search, fetch, read, browser, te...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Security Header Exception Triage QueueAUse when the web response security header regression workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the response-header comparison 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; required headers appear on in-scope responses without breaking declared flows. Use configured search, fetch, read, browser, test, and wri...securityrustgoVotes: 0GitHub stars: 2