← Authorised OSINT ToolkitCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to Authorised OSINT Toolkit
Snapshot Sep 30, 2026 · 23:15 UTC · version 1.1.0
Collection source: not recorded for this historical snapshot.
First saved snapshot
No earlier snapshot is available to establish a change.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"name": "identity-security-review",
"description": "Review user-supplied identity architecture, federation design and control documentation for defensive security gaps. Use for assurance and remediation planning; not for tenant discovery, account enumeration, login testing or credential activity.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 264
}
],
"skill_md_contents": "---\nname: identity-security-review\ndescription: \"Review user-supplied identity architecture, federation design and control documentation for defensive security gaps. Use for assurance and remediation planning; not for tenant discovery, account enumeration, login testing or credential activity.\"\n---\n\n# Identity security review\n\nReview identity architecture from documentation and sanitised configuration summaries.\n\n## Boundaries\n\n- Do not discover tenants, enumerate users, generate login candidates, test authentication or request credentials.\n- Do not infer a person's account status, employment or privileges from public information.\n- Keep recommendations provider-neutral unless the user supplies the relevant platform context.\n\n## Method\n\n1. Map documented identity providers, federation boundaries, trust relationships, privileged roles and recovery paths.\n2. Review MFA strength, conditional access, session controls, legacy authentication, service identities, joiner-mover-leaver controls and emergency access.\n3. Identify trust concentrations, weak ownership, monitoring gaps and controls that depend on undocumented assumptions.\n4. Distinguish design evidence from implemented-control evidence and operational-effectiveness evidence.\n5. Recommend owner-performed verification using approved administrative logs and configuration exports.\n6. Produce an assurance table with control objective, supplied evidence, gap, risk, confidence and remediation.\n"
}SHA-256: 867377b78462e52cb2b0b1008ee496a5e8b7dc16e21ff6b217df0050d1f2bd47