~/cloudsecops/home · boutique security engineering for the AI era
Accepting Q3 engagements
Security engineering for cloud and AI systems.
We assess and secure AWS, GCP, and AI platforms — and build the automation that keeps them secure. Senior engineers, AI-accelerated delivery, engagements in weeks. Our methodology is public.
Fixed scope · Fixed price · Retested to verified
Path
MCP → agent → data
Control
scoped identity
State
✓ verified
- 01scopeAI+ENG
- 02inventory & reconAUTO
- 03ai-assisted analysisAI+ENG
- 04human validationENG
- 05findings & fixesENG
- 06verifyAUTO
- OWASP LLM Top 10AI PENTEST
- OWASP Agentic Top 10AGENT / MCP
- MITRE ATLASAI RED TEAM
- CIS / Well-ArchitectedCLOUD
- Weeks
- not quarters — findings land as they confirm
- Senior
- engineers only — you meet who does the work
- Verified
- every fix retested until the path is dead
001 / The shift
Your infrastructure got a second operator.
The gap between slideware consulting and shrink-wrapped AI products is where incidents live. We work in that gap.
001
Cloud made systems programmable
Infrastructure became code, identities multiplied, and a single over-permissioned role became the modern breach path.
002
AI made them autonomous
Models and agents now read your data, call your tools, and act on your infrastructure — a second operator most security programs never threat-modeled.
003
Security consulting didn't keep up
Big firms still sell quarters of slideware. AI-security products can't design or build for your stack. The gap between the two is where incidents live.
002 / Services
09 services · fixed scope · fixed price
Four practices. One engineering discipline.
- SVC-01Cloud Penetration TestingCloud security2–4 weeks
- SVC-02Cloud Security AssessmentCloud security2–3 weeks
- SVC-03AWS SecurityCloud security2–4 weeks
- SVC-04Google Cloud SecurityCloud security2–4 weeks
- SVC-05AI Penetration TestingAI security2–4 weeks
- SVC-06AI Red TeamingAI security3–5 weeks
- SVC-07AI Agent SecurityAI security2–4 weeks
- SVC-08Security AutomationAutomation & detectionscoped build
- SVC-09Training & AdvisoryAdvisory & training1–3 days
Windows are indicative. Scope and price are fixed after the scoping call.
003 / Mechanism
Where the hours go.
Every consultancy now claims AI acceleration. Here is ours, specifically. Automation does the repetitive work at machine speed; senior engineers spend their hours where judgment matters. That's the whole trick — and it's why the work is faster and costs less.
What we automate
- Asset, identity, and data-path inventory
- Configuration and policy enumeration
- Cross-signal correlation and first-pass triage
- Verification retests after fixes land
What stays human
- Threat models and trust-boundary design
- Exploit-chain construction and validation
- Architecture and remediation decisions
- Every written finding — by the engineer who found it
What you get
- Weeks to findings, not quarters
- Boutique fees — you pay for judgment, not grunt work
- Findings with exploit paths and engineered fixes
- A retest that proves the fix, not a PDF that assumes it
004 / Methodology
The methodology is public.
The fastest way to trust an engineering firm is to read its engineering. Our engagement pipeline, deliverable structure, and tooling stance are published — before you ever talk to us.
Read the full methodology- 01scope: Fixed scope, fixed price — agreed in daysauto+eng
- 02inventory & recon: Asset, identity and data-path enumerationauto
- 03ai-assisted analysis: Correlation and first-pass triage at machine speedauto+eng
- 04human validation: Exploit chains, architecture, judgmenteng
- 05findings & fixes: Written by the engineer who found themeng
- 06verify: Retest until confirmed fixedverified
005 / AI security
[ OWASP LLM Top 10 ][ OWASP Agentic Top 10 ][ MITRE ATLAS ]
We test AI systems the way attackers use them.
Prompt injection chains, agent goal hijack, tool and MCP abuse, data exfiltration through retrieval — mapped to OWASP LLM and Agentic Top 10 and MITRE ATLAS, then fixed with controls that hold: gateway policy, scoped agent identity, human approval where it matters. Prompt filtering alone is not AI security.
Risk path
- 1Untrusted content arrives through retrieval or a tool response LLM01
- 2The agent's goal is hijacked by that injected content ASI01
- 3Hijacked agent calls a tool it legitimately holds access to ASI02
- 4Business data leaves through the tool's own egress path LLM02
Control path
- AGateway policy: request/response inspection and full audit logging
- BScoped agent identity: least-privilege credentials per tool, not per agent
- CHuman approval required on sensitive actions, ending in a verified state
006 / Labs
We publish what we learn.
Security engineering you can read before you buy: research, tooling, and field guides from real assessment work — detection engineering, prompt-injection testing, MCP threat models, AWS assessment checklists.
007 / Ways to engage
Scoped projects, not open-ended retainers.
Assess
ENG-AFind and prove what's exposed. Cloud and AI penetration testing, posture assessments, red teaming — fixed scope, fixed price.
Build
ENG-BEngineering that outlives the engagement: detections, guardrails, AI-driven security workflows and remediation pipelines, built in your environment.
Advise
ENG-CArchitecture reviews, AI security programs, and training for the teams who own the systems afterward.
008 / Next step
Accepting Q3 engagements
Talk to an engineer, not a sales team.
A 30-minute scoping call with the person who'd do the work. Bring your architecture questions — worst case, you leave with better ones.
Practical details
- Response time
- Enquiries are answered within two business days, by a person.
- Where we work
- Remote, working with teams across US and European time zones.
- Prefer email
- hello@cloudsecops.com
Two ways in. Book a slot if you'd rather talk it through, or write to us if you'd rather put it in one place first. Either way you're dealing with the person who'd do the work.