PRACTICE 01
Security Architecture
Design review and architecture for the systems you are about to build — or the ones already in production that nobody has ever threat-modeled.
- Cloud architecture review — AWS and Azure, including Azure Government
- Threat modeling with MAESTRO and STRIDE, tied to concrete controls
- Identity architecture — OAuth / JWT, workload identity, non-human identity governance
- Kubernetes and service-mesh security design (RBAC, mTLS, network policy)
- Security audit, monitoring, and logging architecture
Representative work: lead security architect for an AWS machine-learning platform at Cisco; Azure Government infrastructure security for RTX; statewide SOC and identity architecture for the California Community Colleges Technology Center.
PRACTICE 02
DevSecOps
Security that ships at the speed of your pipeline — scanning, triage, and remediation wired into the build instead of bolted on after release.
- CI/CD pipeline security — SAST, SCA, and secrets scanning in Jenkins and modern pipelines
- Application security posture management (ASPM) program setup and tuning
- Shared scanning libraries and rulesets teams actually keep using
- LLM-assisted finding triage and remediation guidance over your existing data
- Supply-chain and dependency risk scanning for your repositories
Representative work: owned ArmorCode ASPM configuration and application onboarding at The Walt Disney Company across Checkmarx, Snyk, Edgescan, and Semgrep; built a Bedrock-based RAG pipeline that turns application findings into remediation guidance.
PRACTICE 03
Penetration Testing
Hands-on adversarial testing of networks, applications, APIs, and cloud deployments — scoped, authorized, and followed through to verified remediation.
- Web application and API testing — REST and GraphQL
- Cloud penetration testing — AWS and Azure environments
- Active Directory and internal network testing
- Mobile application testing — iOS and Android
- Third-party test management — scoping, remediation tracking, and retest
Representative work: penetration tester for Verizon client engagements and for Cisco's internal research team; AWS and Azure testing across a 23-organization community college system; forensic follow-up on real compromises, including JBoss deserialization intrusions.
PRACTICE 04
AI Security Engineering
Security for LLM and agentic AI systems — where the failure mode is not a crashed server but an agent that did exactly what it was told, by the wrong party.
- Agentic AI red teaming — multi-turn adversarial campaigns against your agents
- Agent runtime detection — behavioral baselining and drift detection with saster-harness
- Guard-model and filter evaluation, including side-channel extraction testing
- MCP server and agent-to-tool trust-boundary assessment
- Agentic identity architecture — workload identity and human-in-the-loop controls for high-risk actions
- AI threat modeling for teams building with LLMs
Representative work: author of the SASTER taxonomy and saster-harness; SPIFFE/SPIRE workload-identity design for an agentic AWS deployment; Bedrock/Claude alert triage inside an OpenSearch-based SOC.
PRACTICE 05 — NEW
AI Agent Security Tool Evaluations
Right now it’s the wild west. Dozens of new agent security products — guardrails, prompt-injection detectors, agent firewalls, MCP scanners, runtime monitors — are shipping with bold detection claims, and there is no reliable, independent evaluation to check them against. Vendor demos test the attacks the vendor chose. We test the ones they didn’t. For buyers, that means a shortlist grounded in evidence before you sign; for vendors, independent validation you can put in front of a skeptical customer.
- Head-to-head evaluation of agent security tools — guard models, filters, firewalls, scanners, and runtime detection — in your environment, on your agents and models
- Coverage mapped to the SASTER 31 patterns: what each tool actually catches, what it misses, and where its claims are specification-only
- Bypass & evasion testing — multi-turn campaigns, indirect injection, and sequences of individually permitted tool calls, not just single-prompt test sets
- False-positive and false-negative measurement against realistic benign workloads, so a tool that blocks everything doesn’t score as “secure”
- Blind-spot analysis across the tool, model, and process planes — including state-based outcomes that action-level allow-lists and dashboards stay green through
- Operational fit: latency, cost per call, deployment model, telemetry quality, and how alerts land in your existing SOC and SIEM
What you get: a written scorecard per tool — SASTER coverage, bypass results with reproduction detail, false-positive rates, and a buy / don’t-buy / buy-with-conditions recommendation you can take into procurement. No vendor sponsorship, no paid placement: we work for the buyer, or for a vendor willing to be tested on the same terms as everyone else.
Why us: this is the work behind our published research — guard-model evaluation including side-channel extraction through a guard LLM’s own refusal signal (DEF CON 34 AI Village), live demonstrations at GrrCON and LayerOne where five layered defenses stayed green through a boundary crossing, and the open saster-harness detector baseline we measure other tools against. It also isn’t new territory: Larry’s comparative evaluations of web application vulnerability scanners are widely cited and predate the AI tool wave by over a decade.
PRACTICE 06 — NEW
Local Open-Source Models for Security Testing & Operations
Some security work should never go to a third-party API — exploit code you’re analyzing, incident data, internal logs, proprietary source code, client findings. We are experts at teaching companies to run the alternative themselves: open-source, open-weight models hosted locally, on hardware and infrastructure you control. This is hands-on enablement, not a slide deck — we configure the stack with your team, then teach them to run, secure, and improve it after we leave.
- Model selection for security work — matching open-source models to the task (code review, log and alert triage, threat-intel summarization, detection engineering, pen-test assistance) and testing them on your data before you commit
- Local hosting & configuration — GPU sizing, inference serving (for example vLLM, Ollama, and llama.cpp-class runtimes), quantization trade-offs, context and performance tuning, on-prem, private-cloud, and air-gapped deployments
- Secure-by-design setup — network isolation, access control and authentication in front of the model, prompt and output logging that doesn’t itself leak sensitive data, and secrets handling
- Workflows for security testing — local models wired into pen-testing, code and configuration review, and red-team preparation, with guardrails and human review where the output drives an action
- Workflows for security operations — SOC triage, incident enrichment, and reporting assistance running entirely inside your environment, integrated with your existing tools and SIEM
- Hands-on training for your team — live workshops and paired build sessions, plus runbooks covering model provenance and licensing checks, updates, evaluation, and day-to-day operations
What you get: a working local model deployment configured for your security testing and operations use cases, a hardened reference configuration your team can reproduce, and trained staff who can operate, evaluate, and extend it — no dependency on us, and no sensitive prompts, code, or incident data sent to an outside model provider to get there.
Why us: the same team behind SASTER and saster-harness — we run local models in our own research and detection work, evaluate guard models and agent tooling for a living, and bring twenty years of cloud, infrastructure, and SOC architecture to the hosting side: sizing it, isolating it, and logging it like any other security-critical system.