Service · Continuous penetration testing
Continuous penetration testing, directed by experienced people
Your systems change every week. Our testing keeps up: the platform covers your internet-facing attack surface continuously, and our team scopes, directs and reviews the work, so every finding you receive has been proven or clearly marked for review.
What is continuous penetration testing?
Continuous penetration testing combines ongoing discovery of your attack surface with recurring, scoped security testing, so new exposures are found and proven while they are still new. It sits between the annual penetration test, which is thorough but quickly dated, and vulnerability scanning, which is frequent but unproven.
Ours adds three things. People lead it: our security director directs the work, and the team decides what to test and reviews what the platform reports. Evidence settles it: a finding is Validated only with the evidence its class requires. We look beyond your perimeter: indirect intelligence such as leaked credentials, public source maps and certificate logs is part of the service, not an add-on. For the trade-offs between approaches, read continuous vs. annual penetration testing.
Why annual tests and scanners leave gaps
-
A snapshot ages fast
An annual test describes the systems you had on the day it ran. Every deploy, new vendor or DNS change after that is untested until next year.
-
Volume without proof
Scanners produce long lists of possible issues. Someone still has to decide which ones are real, which matter and what to fix first.
-
Automation nobody answers for
AI-only testing is fast, but scope, safety and conclusions still need an accountable person. Without one, you inherit the risk of the tool.
How the service runs
-
Scope and verify
We agree targets, testing modes, exclusions and reporting with you, then verify domain ownership. Nothing is tested before that.
-
Discover continuously
The platform maps your internet-facing assets and the indirect signals around them, and compares each run with the last to surface what changed.
-
Test within your mode
Tests run on schedule and when your surface changes, only within the mode you approved. Elevated steps wait for your explicit approval.
-
Prove and triage
A finding is Validated only with class-specific evidence. The team reviews every Signal, discards false leads and confirms what matters.
-
Report, advise and retest
Signed reports, alerts in your channels and guidance for your engineers. When you fix something, we test it again.
AI does the legwork. Experienced people direct it, correct it and answer for it.
Everyone is selling AI. We use it too, to cover more ground, more often. What you are really buying is judgment: a security director with a postgraduate degree in information security and cryptography, a master’s degree in cyber defense and more than 20 years of experience directs all of our security work, and the rest of the team monitors, follows and works every engagement.
What the platform does
- Discovers your internet-facing assets and watches them for change
- Reads signals outside your perimeter: certificate logs, leaked and infostealer credentials, public code, source maps
- Runs approved tests on schedule and on change, only within the mode you authorize
- Matches the technologies you run to new CVEs, with CISA KEV, EPSS and exploit context
- Enforces scope and exclusions, and records every action in an append-only timeline
What our people do
- Scope each engagement with you and verify domain ownership before any testing
- Decide what gets tested, how deep, and when to ask for your approval
- Triage every Signal, validate findings and correct what the machines get wrong
- Prioritize by real-world impact and walk your engineers through the fix
- Sign the report and advise your leadership
What you receive
-
Validated findings
Each with the evidence that proves it, such as the request and response, an out-of-band callback or an access comparison.
-
Reviewed Signals
Possible issues that lack proof, with the evidence still missing and the team’s view on whether to pursue them.
-
Priorities you can defend
Severity (CVSS) combined with CISA KEV, EPSS, exploit availability and our judgment of real-world impact.
-
Remediation guidance
A fix for each finding, written for the engineers who will apply it, and help when they have questions.
-
Retests and change tracking
A retest after each fix, and run-to-run comparison that flags new, resolved and resurfaced findings.
-
Signed reports and alerts
Executive and technical reports signed by our security director, plus alerts to Slack or Discord, email, CSV and API.
What only NorthBound adds to continuous testing
A continuous pentest tells you what is exploitable today. These are the parts most providers leave out, and the reason our findings arrive with context.
-
Read more
Virtual CISO
Fractional security leadership from our team, supported by a posture view across 29 frameworks. The posture view is a heuristic indicator built from your findings, not an audit.
-
Read more
Digital footprint review
Where your domains, email addresses, usernames and phone numbers show up: breach and credential-exposure records, phishing infrastructure and public code.
-
Read more
Tech stack intelligence and alerting
120+ hand-tuned and 4,000+ community fingerprints, matched continuously to new CVEs with CISA KEV, EPSS and exploit-availability context, and alerts when something changes.
-
Read more
Exposure intelligence most providers skip
Public source maps and configuration files (secrets masked), infostealer and breach exposure, certificate transparency, subdomain-takeover fingerprints and public code references.
-
Read more
Executive reporting
Executive and technical reports signed by our security director, plus digests and alerts in the channels your team already uses.
-
Read more
Regulatory security reports, in the language you need
Testing reports and evidence packs for SOC 2, ISO 27001 and PCI DSS, and for Latin American regulators such as El Salvador’s NRP-23 and Mexico’s CNBV.
A typical continuous pentest, and what we add to it
| Typical continuous pentest | NorthBound | |
|---|---|---|
| Human-led testing | Included | Included |
| Virtual CISO advisory | Not typically included | Included |
| Digital footprint review | Not typically included | Included |
| Tech stack intelligence and alerting | Not typically included | Included |
| Exposure intelligence: source maps, infostealers, certificate logs, takeover, public code | Not typically included | Included |
| Regulator-specific reports for Latin America, in the regulator’s language | Not typically included | Included |
| Data hosted where you need it, for example in the US or the EU | Not typically included | Included |
| Model choice, including an isolated proprietary model | Not typically included | Included |
Included Not typically included
“Typical” describes the usual scope of continuous penetration testing services. Individual providers vary, so ask any provider, us included, to show each item in writing.
Every finding is labelled with its proof.
A finding is Validated only when the evidence its class requires has been captured. Everything else is a Signal: reported, capped at medium severity until proven, and reviewed by our team.
Server-side request forgery in an image proxy
- Asset
media.acme.example/proxy?url=- Proof level
- Validated Out-of-band callback received from the target
- Severity
- High
- Evidence
- Callback from 203.0.113.24, recorded with the request that triggered it
- Why validated
- SSRF findings need a safe out-of-band interaction. Without one, they stay Signals.
- Human review
- Triaged and prioritized by the engagement team; retested after the fix
Possible SQL injection in a search parameter
- Asset
shop.acme.example/search?q=- Proof level
- Signal Needs review
- Severity
- Medium capped until proven
- Missing evidence
- An SQL error indicator, a timing difference over 500 ms, or a boolean-based difference
- Next step
- Analyst review, then a targeted retest in the mode you approve
Testing runs only in the mode you approve.
Four modes, from public sources only to operator-assisted testing that needs your explicit approval. No mode allows automated exploitation.
| Mode | Risk | What it can do | What it never does | Approval |
|---|---|---|---|---|
| Passive analysis | Minimal | Public sources only: DNS, WHOIS, certificate transparency logs, open-source intelligence, credential-exposure checks | Sends no requests to your systems | Not required |
| Safe validation | Low | Adds standard HTTP requests, TLS and header review, and TCP port checks | No vulnerability probes, no fuzzing, no authenticated testing | Not required |
| Focused investigation | Moderate | Adds endpoint probing, sensitive-path checks and technology fingerprinting | No fuzzing, no authenticated testing, no exploitation | Not required |
| Operator-assisted | Elevated | Adds vulnerability probes | No exploitation | Your explicit approval |
What is in scope, and what is not
Included
- Internet-facing domains, subdomains and services that you have verified
- Web applications and APIs, including authenticated areas when you provide test credentials
- Indirect intelligence about your organization, from leaked credentials to public code
- Retests after fixes, and continuous comparison between runs
Not included
- Your internal network: available as a separate, in-house internal penetration test
- Denial-of-service or load testing
- Destructive actions, or modifying or extracting your data
- Automated exploitation, in any mode
- Anything outside the scope you approved or on domains you have not verified
Questions about continuous testing
How is this different from a vulnerability scanner?
A scanner lists possible issues. We prove them with evidence, discard the false leads, prioritize what is left and explain the fix, and a person on our team is accountable for each conclusion.
How often do you test?
Discovery and indirect intelligence run continuously. Testing runs on a schedule and when your attack surface changes, within your plan and the mode you approved.
Can we use the report for SOC 2, ISO 27001 or a regulator?
Our signed reports are built to support that evidence. Whether a report meets a specific requirement is your auditor’s or regulator’s decision. See compliance and regulatory reports.
Do you test authenticated areas of our applications?
Yes, when you provide test credentials. They are stored encrypted and used only within the approved scope.
What happens when you find something critical?
Critical and high findings trigger an immediate alert in the channels you choose, and the team follows up with you directly.
Find it before an attacker does.
Tell us what you need covered. We will reply from contact@northboundintelligence.com to arrange a scoping call.
Facts on this page verified 11 November 2026.