Platform
Continuous external vulnerability scanning
Discovery tells you what exists. Continuous external vulnerability scanning tells you which of those assets an attacker could use. EASMLens runs non-destructive checks on the assets in your scope and keeps each finding stable from scan to scan, so you see what is new, what is fixed and what has been open too long.
An annual test leaves eleven months of blind spots
A penetration test examines an agreed scope on agreed days. Internet-facing systems change every week: new releases, new hosts, new vulnerabilities published against software you already run. The Essential Eight expects online services to be scanned for missing patches at least daily, which no manual process sustains.
Raw scanner output is its own problem. The same issue reported afresh on every run buries the one finding that is genuinely new. Teams stop reading the reports.
How EASMLens does it
- 1
Prove ownership
Before any active check, the domain owner publishes a DNS TXT record, or a platform administrator marks the organisation trusted under contract. Passive discovery runs either way. This stops the platform being pointed at someone else's systems.
- 2
Check
Nmap identifies services and versions, Nikto checks web servers, Nuclei runs template-based checks for known vulnerabilities and misconfigurations, and WPScan examines WordPress sites. All checks are non-destructive and never attempt exploitation.
- 3
Normalise
Findings from every tool are normalised into one model with a severity of low, medium, high or critical and a stable identity, so the same issue on the same asset is the same finding next week.
- 4
Track
Findings move through open, accepted, fixed and false positive. Issues that stop appearing are closed automatically once the asset has been rescanned, and new detections are reported against the previous scan.
- 5
Prioritise
Risk scores combine severity with exposure, so an internet-facing critical issue on a production host outranks a low-risk finding on a test page.
What it checks
Exposed services and databases
Remote access, admin panels, databases and other services that should not face the internet.
Known vulnerabilities
Software versions and responses matched against vulnerability data and Nuclei templates.
End-of-life software
Servers and frameworks that no longer receive security updates.
Web server misconfiguration
Default files, directory listings, missing security headers and risky methods.
WordPress
Core, plugin and theme versions with known issues.
Unauthenticated access
Endpoints that respond without authentication when they should not.
What you get
- One findings list across every tool, deduplicated and stable between scans
- New, fixed and still-open counts against the previous scan
- Risk-ranked priorities for remediation
- Per-asset reports in PDF, Word and CSV for auditors and asset owners
- Email alerts for new findings, based on alert rules you set
Where it helps
- Essential Eight and ASD Essentials
- Daily scanning of online services and risk-based vulnerability management for the boundary services domain. See ASD Essentials and internet-facing systems.
- PCI DSS
- Continuous visibility between quarterly ASV scans and annual penetration tests. EASMLens is not an ASV scan and does not replace one.
- Between penetration tests
- Find what changed since the last test, so the next one starts from an accurate scope.
EASMLens discovers your attack surface from DNS, certificate transparency, internet-wide scan datasets and public records, then runs non-destructive checks against the assets in your scope. It never attempts exploitation. It provides discovery, monitoring and evidence. It does not certify an organisation against any framework, and no product can.
Frequently asked questions
- Is this a penetration test?
- No. EASMLens runs automated, non-destructive checks and never attempts exploitation. A penetration test has a person try to break in within agreed rules. The two work well together: EASMLens keeps the scope current between tests.
- Will scanning disrupt our systems?
- The checks are designed to be non-destructive, and they run only against assets you have proved you own or that are in a trusted organisation's scope. Passive discovery never touches your systems beyond what a browser would.
- Why do vulnerability counts not grow on every scan?
- Because a finding keeps its identity between scans. The same issue on the same asset is reported once and tracked until it is fixed, so new detections mean genuinely new exposures.
- Does it replace an ASV scan for PCI DSS?
- No. PCI DSS requires quarterly scans by an Approved Scanning Vendor. EASMLens gives continuous visibility in between and helps you scope the cardholder data environment accurately.
Related capabilities
Attack surface discovery
Find every internet-facing domain, subdomain, IP, certificate, cloud service and API attributed to you, including shadow IT nobody told security about.
Certificate and website monitoring
Catch expired and expiring TLS certificates, sites still on plain HTTP and website quality issues across every web asset you own, not just the main site.
EASM for MSPs and consultants
Run continuous attack surface management for every client from one platform: separate workspaces, ownership proof, client reports and AI summaries.