Assume breach. Prove otherwise.
We attack, harden and watch the systems defense programs depend on: networks, cloud tenants, identities, software factories and the evidence behind an ATO. Every finding cites the DoD or NIST guidance behind it.
Adversaries do not respect org charts. They move from a laptop to a build runner to a cloud account to the mission system. We cover the whole path, and we test it the way they would.
Kyle Hurston · Founder & Principal EngineerSix practice areas. One standard of work.
Offensive security
We break in before someone else does, then prove the fix by trying again.
View practice- Network and infrastructure penetration testing
- Web application and API testing
- Adversary emulation
- Cloud attack path analysis
- Retest and closure verification
Cloud and zero trust
One stolen credential should not become the whole environment.
View practice- AWS GovCloud and Azure Government hardening
- Kubernetes and platform security
- Zero trust architecture and roadmap
- Identity, privilege and access review
- Network segmentation design
Authorization and compliance
Packages built from system evidence, not screenshots in a binder.
View practice- RMF and ATO package support
- STIG implementation and automation
- Continuous ATO enablement
- CMMC and NIST SP 800-171 readiness
- POA&M triage and closure
Secure software delivery
The factory that builds the system gets the same scrutiny as the system it ships.
View practice- Software factory and CI/CD hardening
- Container hardening
- Supply chain security
- Signing and key custody
- Secure code review
Threat detection and response
Detection written for the techniques that matter here, and a team that has rehearsed the bad day.
View practice- Adversary-focused threat modeling
- Detection engineering
- Incident response readiness
- Tabletop exercises
- Vulnerability management programs
Advisory and enablement
Senior security judgment without a full-time hire.
View practice- Fractional security lead
- Security architecture review
- Program office and leadership briefings
- Team training and workshops
- Security tooling
Not sure where to start? Six fixed-scope entry offers, from a free fit call to a CMMC Level 2 readiness review.
Consulting offersMeasured first. Changed second.
Survey
We map the environment as it actually runs: identities, networks, cloud accounts, pipelines and data flows.
Attack
We work the paths an adversary would take through that map and rank them by what each step would gain them.
Harden
Fixes land as reviewed changes your team owns. Nothing is applied out of band.
Prove
We attack again. The engagement closes when the exploits stop working, with evidence your assessor can read.
Tools in development. Most of them will be free.
Citadel
Posture management for software factories. Scores every project against NIST SSDF and the DoD DevSecOps reference designs and tracks drift over time.
Hardline
Container hardening kit: base images, CI templates and admission policy bundles aligned to the DoD Container Hardening Guide.
Gatekeeper
Pre-commit and CI gate that rejects unsigned commits, exposed secrets and unpinned dependencies.
Free · MIT · In developmentSBOM Diff
Compares two SBOMs and reports new components, license changes and known vulnerabilities between releases.
Free · Apache-2.0 · In developmentTripwire CI
Canary credentials placed in CI/CD systems that alert on first use, giving early warning of pipeline compromise.
Taught by the people who do the work.
Software Factory Foundations
The DevSecOps software factory model, the DoD reference designs, and how to stand up a gated pipeline correctly the first time.
$149 T2
Pipeline Attack and Defense
Students attack an instrumented, deliberately weak software factory, then harden it until their own techniques fail.
$899 T3
Container Hardening Practicum
Build images that satisfy the DoD Container Hardening Guide and produce the evidence to prove it.
$749 T4
Team Intensive
On-site or remote training built around your production pipeline. Remediations are merged during the session.
Quoted All training
Poisoned Pipeline Execution: A Technical Walkthrough
How a public CI configuration is exploited, and the controls that stop it.
Office Hours · Dec 10, 2026Pipeline Architecture Office Hours
Open session. Bring a configuration for live review.
Seminar · Dec 17, 2026Signing Strategy: Keys, Custody and Rotation
Commit, artifact and image signing designed to survive a key compromise.
Workshop · Jan 9, 2027Container Hardening Workshop
Hands-on: build, scan, sign and gate a hardened image.
Full calendarNotes from the field.
Draw the CMMC boundary before you write the SSP
Most of the cost of CMMC Level 2 is decided by scope. Here's how I map where CUI actually goes before any control work starts.
offensive · Nov 5, 2026What a retest proves that a report cannot
A penetration test report describes a moment. The retest is the only part of the engagement that shows the fix actually holds.
ci-cd · Nov 3, 2026Your forked merge requests are running with your secrets
One pipeline decision controls whether a stranger's merge request can read your deploy keys. Here's how to check it in five minutes.
Contracting data.
- UEI / CAGE
- SAM.gov registration in progress
- NAICS
- 541512 · 541519 · 541511 · 541690 · 611420Computer Systems Design Services · Other Computer Related Services · Custom Computer Programming Services · Other Scientific and Technical Consulting Services · Computer Training
- Firm
- N3m3sisDevSecIndependent · Founder-led