Learn · Reference
Glossary of penetration testing and exposure terms
Short definitions of the terms used across this site and in our reports, from attack surface and CTEM to the Validated and Signal labels on every finding. Each entry links to related terms and, where there is one, to a longer explainer.
Terms, A to Z
- Attack surface
Everything an attacker could try to reach or use: domains, subdomains, IP addresses, services, applications, APIs, cloud resources and the credentials that open them. The external attack surface is the part reachable from the internet.
- Certificate Transparency (CT)
A system of public, append-only logs that record TLS certificates as certificate authorities issue them, defined in RFC 6962 and revised in RFC 9162. It exposes mis-issued certificates and, as a side effect, makes every hostname in a public certificate visible.
Related: Certificate Transparency explained · Subdomain takeover
- CISA KEV catalog
The Known Exploited Vulnerabilities catalog published by the US Cybersecurity and Infrastructure Security Agency (CISA), listing CVEs with reliable evidence of exploitation in the wild. A KEV entry is a strong reason to fix first.
- Continuous penetration testing
Penetration testing that runs on an ongoing basis, on a schedule and when systems change, instead of once a year. It keeps coverage current between point-in-time tests; it does not make their depth unnecessary.
Related: Continuous vs. annual pentest · Point-in-time penetration test
- Continuous threat exposure management (CTEM)
A program for continuously finding, prioritizing, validating and fixing exposures, introduced by Gartner in 2022. Its five stages are scoping, discovery, prioritization, validation and mobilization.
Related: CTEM explained · EASM
- Credential exposure
Usernames, passwords, tokens or session cookies for your organization’s systems that are available to people who should not have them, for example in third-party breach data or infostealer logs.
Related: Infostealer · Session hijacking
- CVE
Common Vulnerabilities and Exposures: the public program that gives each disclosed vulnerability an identifier in the form CVE-year-number. The NVD, run by NIST, adds severity scores and affected-product data to each record.
- CVSS
The Common Vulnerability Scoring System, maintained by FIRST, rates a vulnerability’s technical severity on a scale from 0 to 10. It describes how bad a vulnerability could be, not how likely it is to be exploited.
- Dangling DNS record
A DNS record that still points to a resource that no longer exists, such as a deleted cloud storage bucket, a canceled hosting account or a released IP address. It is the usual cause of a subdomain takeover.
Related: Subdomain takeover · Subdomain takeover explained
- Digital footprint
What public sources reveal about an organization’s domains, IP addresses, URLs, email addresses, usernames and phone numbers, including where they appear in breach records, public code or phishing infrastructure.
Related: Credential exposure · Digital footprint review
- Domain ownership verification
Proof that you control a domain, such as a DNS TXT record or a verification file served over HTTP, given before any testing starts. NorthBound tests nothing until ownership is verified.
Related: Testing mode
- EPSS
The Exploit Prediction Scoring System, published by FIRST, estimates how likely it is that exploitation of a CVE will be observed in the next 30 days. Read with CVSS and CISA KEV, it helps decide what to fix first.
- Exposure intelligence
What an attacker can learn about an organization from outside its perimeter: certificate transparency logs, public source maps and configuration files, leaked and infostealer credentials, public code and new vulnerabilities in the technologies it runs.
Related: Digital footprint · Exposure intelligence at NorthBound
- External attack surface management (EASM)
The continuous discovery and monitoring of an organization’s internet-facing assets, including those its security team does not know about. It shows what to test; it does not prove what is exploitable.
Related: EASM vs. vulnerability scanning · Attack surface
- False positive
A reported finding that turns out not to be a real issue, often because a tool inferred a vulnerability from a version number or a pattern without proof. Requiring evidence, and human review, reduces them.
Related: Validated finding · Signal
- Infostealer
Malware that steals saved passwords, session cookies, autofill data and other browser data from an infected computer and sends them to its operator as a log. The logs are traded in criminal marketplaces and channels.
Related: Infostealer exposure explained · Session hijacking
- Internal penetration testing
A penetration test of the networks and systems inside your perimeter, run as if an attacker or a compromised device were already inside. NorthBound performs it in-house, under written rules of engagement.
Related: Penetration testing · Internal penetration testing service
- Penetration testing
An authorized, simulated attack in which testers look for weaknesses in a defined scope, show what an attacker could do with them and explain how to fix them. Unlike a vulnerability scan, it confirms impact with evidence.
Related: Continuous penetration testing · Vulnerability scanning
- Point-in-time penetration test
A penetration test of an agreed scope during a fixed window, often once a year, documented in a dated report. It shows depth at one moment; changes after the window are not covered.
Related: Continuous penetration testing · Continuous vs. annual pentest
- Retest
A repeat test of a specific finding after a fix, to confirm that the issue is resolved. Comparing later runs also shows findings that resurface.
Related: Validated finding
- Session hijacking
Taking over a signed-in session by reusing its session cookie or token, often one stolen by an infostealer. Because the session has already passed sign-in, it can bypass the password and MFA until it expires or is revoked.
Related: Infostealer · Credential exposure
- Shadow IT
Systems, cloud services and applications set up or used without the security team’s knowledge, such as a campaign site on a third-party platform. Finding them is a core job of external attack surface management.
Related: EASM · Attack surface
- Signal
NorthBound’s label for a finding that has not yet met the evidence its class requires. Signals are reported, capped at medium severity until proven, and reviewed by our team.
Related: Validated finding · False positive
- Source map
A file that maps minified JavaScript or CSS back to its original source, created by build tools for debugging and standardized as ECMA-426. Published on a production site, it lets anyone rebuild the original code.
Related: Source map exposure explained · Exposure intelligence
- Subdomain takeover
Taking control of a subdomain whose DNS record points to an external resource that no longer exists, by claiming that resource and serving content under the victim’s domain.
Related: Dangling DNS record · Subdomain takeover explained
- Technology fingerprinting
Identifying the software, frameworks and versions a site runs from its responses, headers, files and other observable traits, so that new CVEs can be matched to what is actually deployed.
Related: CVE · Tech stack intelligence
- Testing mode
The level of testing a client approves for a scope. NorthBound’s modes range from passive analysis, which sends nothing to your systems, to operator-assisted testing, which needs your explicit approval. No mode allows automated exploitation.
Related: Domain ownership verification · Methodology
- Validated finding
NorthBound’s label for a finding backed by the evidence its class requires, for example a safe out-of-band callback for server-side request forgery. Findings without that evidence are reported as Signals.
- Virtual CISO (vCISO)
Fractional security leadership from an outside team: priorities, roadmap, board briefings and the decisions a chief information security officer would make, without a full-time hire.
Related: Virtual CISO service · CTEM
- Vulnerability scanning
Automated checks of a known list of assets for known weaknesses, usually by matching versions and signatures. It is fast and broad, but blind to assets outside the list and cannot prove exploitability on its own.
Related: EASM · EASM vs. vulnerability scanning
Facts on this page verified 11 November 2026.