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,225–1,248 of 28,990 skills

Aas Secure Delivery Oauth Scope Drift Threshold Rule CheckAUse when a OAuth scope drift review decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the OAuth scope-to-feature map 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; each scope has a current purpose and unused privilege is flagged for owner review. Use configured search, fetch, read, browser, test,...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Oauth Scope Drift Source Provenance LedgerAUse when a decision about OAuth scope drift review depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the OAuth scope-to-feature map. Success means each material claim has a source, version/date, location, and confidence note; each scope has a current purpose and unused privilege is flagged for owner review. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Oauth Scope Drift Scope Intake GateAUse when a new OAuth scope drift review request needs a bounded work scope to produce a scoped intake card for the OAuth scope-to-feature map. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; each scope has a current purpose and unused privilege is flagged for owner review. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three focused...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Oauth Scope Drift Scenario Sensitivity MatrixAUse when the OAuth scope drift review team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the OAuth scope-to-feature map with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; each scope has a current purpose and unused privilege is flagged for owner review. Use configured search, fetch, read, browser, test, and write capabilities o...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Oauth Scope Drift Recovery Readiness DrillAUse when the OAuth scope drift review workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the OAuth scope-to-feature map 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; each scope has a current purpose and unused privilege is flagged for owner review. Use configured search, fetch, read, browser, test, and wri...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Oauth Scope Drift Exception Triage QueueAUse when the OAuth scope drift review workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the OAuth scope-to-feature map 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; each scope has a current purpose and unused privilege is flagged for owner review. Use configured search, fetch, read, browser, test, and write capabili...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Oauth Scope Drift Completeness ReconciliationAUse when the OAuth scope drift review workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the OAuth scope-to-feature map 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; each scope has a current purpose and unused privilege is flagged for owner review. Use configured search, fetch, read, browser, test, and w...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Oauth Scope Drift Closeout Handoff LedgerAUse when a OAuth scope drift review work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the OAuth scope-to-feature map 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; each scope has a current purpose and unused privilege is flagged for owner review. Use configured search, fetch, read, browser, test, and write capabilit...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Oauth Scope Drift Change Impact TraceAUse when a version, rule, source, or stakeholder change may affect OAuth scope drift review to produce a before/after change record and impact map for the OAuth scope-to-feature map. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; each scope has a current purpose and unused privilege is flagged for owner review. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and a...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Oauth Scope Drift Approval Evidence PacketAUse when a OAuth scope drift review result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the OAuth scope-to-feature map 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 scope has a current purpose and unused privilege is flagged for owner review. Use configured search, fetch, read, browser, te...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Extension Permissions Threshold Rule CheckAUse when a third-party extension permission review decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the extension permission inventory 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; every granted capability has a task need and update authority is identified. Use configured search, fetch, read, b...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Extension Permissions Source Provenance LedgerAUse when a decision about third-party extension permission review depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the extension permission inventory. Success means each material claim has a source, version/date, location, and confidence note; every granted capability has a task need and update authority is identified. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record ev...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Extension Permissions Scope Intake GateAUse when a new third-party extension permission review request needs a bounded work scope to produce a scoped intake card for the extension permission inventory. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; every granted capability has a task need and update authority is identified. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to ...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Extension Permissions Scenario Sensitivity MatrixAUse when the third-party extension permission review team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the extension permission inventory with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; every granted capability has a task need and update authority is identified. Use configured search, fetch, read, browser, test, and write c...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Extension Permissions Recovery Readiness DrillAUse when the third-party extension permission review workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the extension permission inventory 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; every granted capability has a task need and update authority is identified. Use configured search, fetch, read, browser, ...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Extension Permissions Exception Triage QueueAUse when the third-party extension permission review workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the extension permission inventory 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; every granted capability has a task need and update authority is identified. Use configured search, fetch, read, browser, test, and w...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Extension Permissions Completeness ReconciliationAUse when the third-party extension permission review workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the extension permission inventory 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; every granted capability has a task need and update authority is identified. Use configured search, fetch, read, browser...securityrustgoVotes: 0GitHub stars: 2
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