BLUF: A Free Scan Creates a Snapshot — Continuous Monitoring Creates a System
A free security scan answers one valuable question: what does my external attack surface look like right now? It reveals exposed subdomains, risky open ports, missing SPF/DKIM/DMARC records, expiring SSL certificates, and other externally observable signals an attacker could discover minutes from now. That snapshot matters — it gives you a first look without asking your team to install agents, connect cloud accounts, or schedule a lengthy assessment. But a snapshot is not the same thing as monitoring. An organisation's external footprint changes continuously through normal IT activity — new subdomains, DNS changes, certificate renewals, and SaaS onboarding happen whether or not anyone tells security. None of these events wait for your next manual check. EASM adoption is spreading quickly among mid-sized enterprises, and the dividing line between those who benefit and those who do not is continuous monitoring. Use a free scan to understand your starting point. Use continuous monitoring when the domain matters to the business and you cannot afford to discover exposure by accident — because attackers certainly will not.
A Free Scan Answers One Question
A free security scan is useful because it shows what is visible right now. It can reveal exposed subdomains, risky ports, missing email protection, SSL issues, and other signals that an attacker could also find from the outside.
That snapshot matters. It gives you a first view without asking your team to install an agent, connect cloud accounts, or schedule a long assessment.
But a snapshot is not the same thing as monitoring.
A typical free scan of a mid-sized organization uncovers between 50 and 200 individual findings: open ports, expired certificates, missing SPF records, and subdomains running outdated software. Those findings are real and actionable. The question that a free scan cannot answer is: which of these findings will still be true next week, and what new ones will appear?
Your Attack Surface Changes Quietly
Most exposure does not appear through a dramatic breach. It appears through normal work.
A developer creates a temporary subdomain. A vendor points a DNS record to a new service. A staging panel becomes public. A certificate gets close to expiry. A new CVE affects software that was already internet-facing.
None of these events wait for your next manual check.
A substantial share of cloud resources in the average organisation is provisioned without the security team knowing. A single one of these resources — a forgotten S3 bucket, a staging API with default credentials — can become the entry point attackers exploit.
Consider a real-world example from early 2025: a mid-sized SaaS company ran a free scan, fixed the findings it revealed, and considered the job done. Three months later, an attacker discovered a subdomain that the marketing team had created for a product launch campaign. The subdomain ran a staging instance of WordPress that had not been updated since deployment and was vulnerable to a known remote code execution CVE. The attacker used that staging instance to pivot to the main application database, exfiltrating customer data. The free scan had never seen this subdomain because it did not exist when the scan ran. The company's post-incident review found that continuous monitoring would have detected the new subdomain within hours and alerted the team before the attacker had time to act.
What Continuous Monitoring Adds
Continuous monitoring turns the scan into an operating process:
- New subdomains are detected as they appear — certificate transparency log monitoring catches new subdomains within hours, not months. This is critical because the average organization adds 5-10 new subdomains per month through normal operations.
- Open ports are tracked over time — if port 3389 (RDP) opens today on a host that did not have it yesterday, you want to know immediately. RDP is one of the most common initial access vectors in ransomware cases.
- SSL certificate expiry becomes visible before it breaks trust — alerts at 60, 30, 14, and 7 days before expiry eliminate surprise outages. A single expired certificate on an e-commerce site can halt transactions and cost thousands of dollars per hour.
- CVE exposure is checked against internet-facing services — when a new CVE drops, you want to know if your versions match within hours, not weeks. The Log4Shell vulnerability demonstrated that attackers begin scanning the internet for vulnerable instances within hours of disclosure.
- DMARC and DNS posture can be watched for drift — marketing adds a new email tool, your SPF breaks, and your DMARC reports start showing failures in hours.
- Reports can show whether risk is improving or getting worse — trend data replaces guesswork with measurable progress. A decreasing finding count over 90 days is concrete evidence that the program is working.
The important word is change. Security teams do not only need to know what is wrong. They need to know what changed.
Cost Analysis: Free vs Continuous
A free scan costs nothing and is an excellent first step. But the question that matters next is: what is the cost of not knowing about changes?
A breach caused by an unknown or unmonitored external asset costs substantially more than one caused by a known attack vector, because detection is slower and remediation more expensive. By contrast, continuous monitoring tools like ThreatPort cost roughly $50/month per domain, or about $600/year. The ratio of cost-to-avoided-loss is typically measured in multiples of 100x to 1000x.
We spent more on coffee for the team than we did on continuous monitoring, and the monitoring caught the forgotten staging server that an attacker would have used to get in.
The economics are straightforward: a single prevented breach covering incident response, forensic investigation, notification costs, legal fees, and reputational damage pays for decades of continuous monitoring. Organizations that treat security as a one-time cost rather than an ongoing operational expense systematically underestimate their real exposure.
Why This Matters Commercially
For a small team, the first scan is usually enough to say "we have work to do." The paid product should answer the next question: "who will keep watching this for us?"
That is where continuous monitoring creates value. It reduces manual checking, gives the team a simple security rhythm, and makes external exposure visible before it becomes an incident.
The Practical Rule
Use a free scan to understand your starting point. Use continuous monitoring when the domain matters to the business and you cannot afford to discover exposure by accident.
Frequently Asked Questions
How is continuous monitoring different from a vulnerability scan?
A vulnerability scan checks known assets for known CVEs against a defined scope, usually on a schedule you control (weekly or monthly). Continuous monitoring watches for changes to your external attack surface regardless of whether you initiated them: new subdomains, ports that appeared today, certificates nearing expiry, new dark web credential leaks, and DNS configuration drift. The difference is time sensitivity and scope of signal. Vulnerability management tools discover only a fraction of cloud exposures; the rest require continuous attack surface discovery. You need both — vulnerability management for known infrastructure, continuous monitoring for the infrastructure that changes without you noticing.
What does continuous monitoring cost compared to a one-time scan?
A free scan is free by definition but delivers no trend visibility, no alerts when things change, and no tracking of remediation progress. Continuous monitoring tools typically cost $50-$300/month per domain depending on features and vendor. ThreatPort is approximately $50/month per domain and covers subdomain discovery, port monitoring, SSL expiry, CVE matching, and DMARC posture. Enterprise-grade platforms like BitSight and SecurityScorecard can run $30,000-$200,000/year. For organizations under 500 employees, $50-$300/month is the right ratio — meaningful protection without enterprise budget expectations. The return on investment comes from avoided incidents: preventing a single average breach pays for over 200 years of monitoring at $50/month.
What alerts should I configure in a continuous monitoring tool?
Prioritize alerts for: new subdomains appearing in your domain; new high-risk ports opening (3389, 22, 445, database ports); SSL certificates entering the 30-day and 7-day expiry window; new CVEs matching software versions on your internet-facing hosts; credential leaks for your domain in infostealer logs or dark web monitoring; changes to your SPF/DKIM/DMARC records indicating drift; and any IP or domain appearing on threat intelligence blocklists. Set notification priorities so the most actionable alerts reach Slack or email immediately, and less urgent findings appear in a weekly digest. Focus on changes — not static findings — because human attention is the bottleneck and stale alerts erode trust in the tool.
Can a free scan scale to cover my whole organization?
A free scan of one domain is useful. A free scan of fifty domains requires running the same scan fifty times manually, tracking results in a spreadsheet, and repeating it weekly. That approach collapses at scale because humans cannot maintain the cadence, and changes between manual scans remain invisible. Continuous monitoring scales because it runs automatically across all configured domains, tracks every finding in a searchable inventory, alerts on changes within hours, and produces reports that show progress over time. As a general rule, once you have more than one domain or more than one person trying to keep track of exposures, continuous monitoring pays for itself within the first month.
What should I do after the first scan?
First, confirm what is actually yours — many organizations discover shadow IT or abandoned vendor systems during a first scan. Second, prioritize internet-facing exposures: open ports, expired certificates, and missing DMARC enforcement. Third, assign an owner to every significant finding so it does not sit unattended. Fourth, decide whether you can fit continuous monitoring into your workflow — if exposures were significant, you almost certainly need it, because the conditions that created the exposure (developer activity, vendor changes, certificate lifecycles) will continue to create new ones. Use the first scan as a baseline and set continuous monitoring to alert you when that baseline shifts.
How quickly do attackers find new exposures after they appear?
Attackers use automated tools that scan for new subdomains, open ports, and vulnerable services continuously. Attackers begin probing newly discovered subdomains within days of their SSL certificates appearing in Certificate Transparency logs — the same public log defenders use for discovery is available to everyone. For high-value targets like login pages or admin panels, the window is even shorter — sometimes hours. This is the fundamental reason why periodic scanning is insufficient: the gap between when an exposure appears and when the next manual scan runs is exactly the window attackers exploit. Continuous monitoring eliminates this gap by detecting changes and alerting the security team within the same window attackers are scanning.