[ PLATFORM CAPABILITY ]
Authorized offensive testing
Pentest results beside CSPM — prioritized with signed scope every time.
Annual PDF pentests rarely keep pace with shipping velocity, and findings that live outside CSPM queues get deprioritized. NNSEC continuous offensive testing runs inside NorthSec AI with signed rules of engagement, hash-chained authorization records, and live console workflows. Operators schedule scans, map attack surface, and export auditor-friendly reports without losing context between retainer calls and platform work — engineering sees exploitability next to misconfiguration severity.
[ WHO IT IS FOR ]
Teams moving from yearly assessments to continuous testing; regulated environments requiring provable authorization before any offensive action.
[ OPERATING CADENCE ]
Pentest results land beside CSPM findings so prioritization respects both exposure and exploitability.
Delivered as part of your NNSEC retainer and NorthSec AI tenant — not a separate SKU.
Problems this
capability removes.
Teams adopt this when the status quo costs audit time, incident credibility, or engineering trust.
- ◆Pentest reports that engineering cannot map to owners
- ◆Production scans without documented scope
- ◆Retest cycles measured in quarters instead of sprints
- ◆CSPM criticals that are not exploitable in practice
What changes
after adoption.
Measurable shifts in audit prep, triage time, and executive confidence — not vanity dashboard counts.
Unified prioritization
Exploitability and exposure share one backlog — no more parallel Jira projects per vendor.
Provable authorization
Every run references signed scope — assets, methods, timing — stored in an auditable vault.
Faster retest
Validate fixes on deploy pipelines instead of waiting for the next annual engagement.
What you
operate.
Concrete surfaces and objects your teams touch weekly — described in operator language.
Authorization vault
E-sign RoE, scope tags, and expiry — scans abort if authorization lapses.
Schedules and on-demand
Black-box and grey-box cycles with change detection on external attack surface.
Attack surface graph
Domains, APIs, and cloud assets linked to findings and threat intel lanes.
Auditor exports
Reports with reproduction steps, evidence, and remediation status — not raw CSV dumps.
How teams
use it weekly.
Typical cadence once connectors and authorizations are in place — aligned to your retainer milestones.
01
Scope and sign
Legal and security agree RoE; technical scope locked before any probe.
02
Run and triage
Findings land in shared queue with CSPM; owners assigned in same SLA model.
03
Retest on merge
CI or scheduled retest confirms closure before marking resolved.
[ GOVERNANCE ]
- ◆Destructive tests require explicit addendum
- ◆Production-impacting actions blocked without written rules
- ◆Hash-chained audit history for regulator inquiries
FAQ
Yes — /app/pentest is the live workspace; this capability describes how it integrates with the broader program.
Include Authorized offensive testing in your retainer
Book a briefing to map this capability to your clouds, frameworks, and SOC maturity.