Skip to main content

Agentic AI & Cloud Security

Nash Ogden

Works on making teams more productive with agentic AI. Writes the FactualMinds guides on AWS security and compliance: identity, threat detection, data protection, and audit readiness, the controls AI agents need before they touch production systems.

Published articles
53
Nash Ogden

Agentic AI & Cloud Security

View LinkedIn profile

Expertise

Agentic AIAI Agent GovernanceAWS SecurityComplianceIAMThreat Detection

More articles

4 min

VDI and Secure Remote Workforce on AWS (2026): WorkSpaces Secure Browser vs Applications vs Full Desktop

Most remote-access RFPs still default to full Windows desktops, but 60%+ of contractor work is browser-only. WorkSpaces Secure Browser isolates SaaS in AWS; WorkSpaces Applications (formerly AppStream 2.0) streams fat clients without a desktop. A composite regulated services firm cut 3 legacy VDI vendors to 2 OU-scoped patterns and reduced unmanaged-endpoint incidents from ~9/quarter to ~2 after splitting browser vs app streaming.

5 min

Continuous Compliance Automation on AWS (2026): Config Conformance Packs, SSM Auto-Remediation, and Audit Manager — Past Security Hub

Security Hub detects control failures. It is not the compliance pipeline, and treating it as one is why teams still scramble for evidence at audit time. The four jobs are distinct: AWS Config detects drift, conformance packs deploy rules org-wide as immutable bundles, SSM Automation remediates the safe class, and evidence accrues via conformance-pack exports plus Security Hub control status (Audit Manager only if you onboarded before it closed to new customers on 30 April 2026). This post has the tool-per-job matrix, a conformance pack with auto-remediation, and the auto-remediation gotcha to design around.

6 min

AWS Incident Response Runbooks (2026): What Changes Now That Security Incident Response Is Metered and GuardDuty Correlates Attack Sequences

Two 2025 shifts rewrite the IR playbook: GuardDuty Extended Threat Detection now emits a single critical attack-sequence finding instead of a pile of high findings, and AWS Security Incident Response moved to metered pricing (free first 10,000 findings/month, then $0.000676 each) on November 21, 2025. The lesson is to page humans on the top 1% of correlated criticals, isolate instead of terminate, and let auto-triage absorb the rest.

Work With Us

Our articles share what we know. Our consulting engagements apply that knowledge to your specific AWS environment.