Article
AI Agent Observability Is a Security Control
Security telemetry must connect agent identity, tool requests, authorization decisions, resource effects, and recovery—not just model latency.
Published
Author profile
Bryan Oubaita
Creator and owner of Baitaphish, publishing practical work on cybersecurity, cloud and AWS security, identity, phishing defense, AI security, and agent governance.
About
Security work grounded in inspectable evidence
Bryan Oubaita created Baitaphish and publishes practical cybersecurity education and source-linked research.
His work focuses on cloud and AWS security, identity, phishing defense, AI security, and agent governance. Baitaphish separates original analysis from source records and makes provenance, review dates, automation, and limitations visible.
Focus areas
Topics
- Cybersecurity
- Cloud and AWS security
- Infrastructure security
- Identity security
- Phishing defense
- AI security
- Agent governance
Verified public profile
Elsewhere
Published on Baitaphish
Research and articles
Article
The Real Permission Boundary of an AI Agent
An agent's effective authority spans identity, delegation, tools, credentials, policies, resources, and downstream effects—not its prompt alone.
Published
Article
Cryptographic Exposure Maps: Preparing a Repository for Algorithm Migration
A useful cryptographic inventory connects algorithms to libraries, protocols, keys, certificates, data, owners, and replacement constraints.
Published
Article
CVSS Is Not a Patch Queue: A Better Prioritization Model
Use CVSS as severity evidence—not a remediation order—by adding exploitation, exposure, business context, and control evidence.
Published
Article
GitHub Actions OIDC Removes a Secret, Not the AWS Trust Problem
GitHub OIDC eliminates stored AWS access keys, but workflow claims, role trust, session permissions, and resource reach still define risk.
Published
Article
IAM Wildcards Aren't the Whole Problem
Effective AWS authority depends on principal, action, resource, context, and every applicable policy—not the visible wildcard count alone.
Published
Article
Prompt Injection Is an Authorization Problem
Prompt injection manipulates model behavior; authorization, mediation, and resource reach determine whether manipulation becomes a harmful action.
Published
Article
Why Security Scanners Must Report Coverage Gaps
A zero-finding scan is uninterpretable unless the scanner records what it analyzed, skipped, could not build, and does not support.
Published
Article
What Source-Linked Security Intelligence Actually Requires
A source URL is not provenance. Useful intelligence preserves record identity, version, retrieval, claim scope, transformations, and uncertainty.
Published
Article
Static Security Exposure Graphs: Why Findings Aren't Enough
Repository findings become more actionable when connected to identities, credentials, policies, resources, data, and reachable effects.
Published
Research
Capability × Authority × Reach
A provider-neutral systems-security framework for constraining autonomous AI agents through capability assessment, effective authority, bounded reach, exposure-path analysis, and runtime trajectory assurance.
Published
Research
Secure AWS Architecture: Decisions, Controls, Evidence, and Recovery
A decision model for multi-account AWS security: trust boundaries, identity, preventive and detective controls, evidence, containment, and recovery.
Published
Research
Threat Modeling AI Agents: Trust Boundaries, Controls, and Evidence
A vendor-neutral threat model for AI agents that separates model behavior from authorization and maps threats to controls, evidence, tests, and residual risk.
Published
Research
Threat Modeling That Produces Testable Controls
A practical method for turning system boundaries and abuse paths into owned controls, observable evidence, and repeatable tests.
Published
Research
Why Provenance Matters in Security Intelligence
Provenance turns a security claim into a traceable record of source, transformation, review, and intended use—without pretending lineage alone guarantees truth.
Published
Research
NIST SP 800-61r3: Incident Response and Cybersecurity Risk Management
NIST's current incident-response guidance integrates preparation, response, recovery, and continuous improvement across the six CSF 2.0 Functions.
Published
Research
Repo Brief: Open Policy Agent (OPA) — Policy-as-code for authorization and guardrails
OPA lets you centralize policy decisions (Rego) for authz and compliance across microservices, Kubernetes, CI, and more.
Published
Research
Repo Brief: SigmaHQ/Sigma (Portable Detection Rules)
Sigma is a detection-rule format that lets you write once and translate to multiple SIEM backends (Splunk, Sentinel, etc.).
Published
Research
SLSA: Supply-chain Levels for Software Artifacts (What to actually implement)
SLSA is a maturity model for build provenance and tamper resistance. The real value is disciplined build pipelines and signed attestations.
Published
Editorial approach
Separate evidence, interpretation, and automation
Baitaphish writing names its sources, records review dates, labels AI assistance, and states what the available evidence cannot establish. Corrections should preserve the history of a claim rather than silently replacing it.