What the Insurer's Scan Saw Before You Filled In the Application
If your broker sent back a higher price, a lower limit or a list of "subjectivities" to clear before binding, an outside-in scan is often the reason. Many cyber carriers and brokers run a cyber insurance security scan against your domains and IP ranges before quoting. It's passive and unauthenticated. It sees what an attacker on the internet would see: open ports, service banners, software versions, certificate problems, email-authentication records and leaked credentials.
The scan doesn't know your compensating controls, and it sometimes attributes assets to you that aren't yours. Over the next 30 days, fix the real exposures, challenge the wrong ones with evidence, and hand the underwriter a clean file before the policy binds. Underwriters re-rate on evidence, not promises.
Looking to streamline vendor RFP selection?
Access pre-negotiated tier discounts through our independent institutional network.
Days 1–3: Get the Full Report and Build a Findings Register
Ask your broker for the complete scan output, not the one-page summary. You need each finding's IP address, hostname, port, detection date and severity rating. Some carriers share the raw report; others share only flagged items. Push for the raw version, because you can't dispute what you can't see.
Put every finding into one register with these columns: asset, finding, owner, verdict (real, false positive or accepted risk), fix, target date and evidence. Assign one accountable owner per line. Then sort by what underwriters typically weight most heavily.
| Window | Workstream | Typical underwriting weight |
|---|---|---|
| Days 1–7 | Exposed RDP, SMB, databases, admin panels | Often a decline or bind blocker |
| Days 4–10 | Unpatched VPN and firewall appliances | Often a bind blocker if the flaw is known to be exploited |
| Days 8–15 | SPF, DKIM, DMARC | Pricing factor, sometimes a subjectivity |
| Days 10–20 | False-positive disputes | Removes unfair loading |
| Days 21–30 | Evidence pack and rescan request | Triggers re-rating |
Weighting varies by carrier and market, so treat the right-hand column as a working assumption and confirm it with your broker.
Days 1–7: Close Exposed RDP and Other Remote-Access Doors
Exposed RDP is close to a hard stop for many underwriters, because remote desktop open to the internet is a common ransomware entry point. If the scan found port 3389 (or RDP moved to a non-standard port), treat it as an incident-level priority.
- Confirm the host and its business purpose. Often it's a forgotten vendor-support server or a cloud VM someone spun up for testing.
- Remove the public rule at the firewall or cloud security group. Don't just change the port; scanners fingerprint the protocol, not the number.
- Put remote admin behind a VPN with MFA, a zero-trust access broker or a cloud bastion service.
- Check the host's logs for successful logins from unfamiliar addresses during the exposure window. If you find any, call your incident response provider before you call your broker.
Apply the same treatment to exposed SMB (445), Telnet, database ports such as 1433, 3306 and 9200, and web admin consoles for routers, hypervisors or backup appliances.
Days 4–10: Patch or Isolate Internet-Facing VPN and Firewall Appliances
Scanners read version banners from VPN gateways and firewalls and match them against public vulnerability lists, notably CISA's Known Exploited Vulnerabilities catalog, which many carriers use as a reference wherever you operate. Fortinet, Ivanti, Citrix NetScaler, Palo Alto Networks, Cisco and SonicWall products have all had widely exploited flaws, so a stale firmware version on any of them draws attention.
Patch to the vendor's fixed release, then verify the banner actually changed. Some appliances keep reporting an old version string after an upgrade, which creates a false positive you'll need to document. If you can't patch quickly because of a change freeze or end-of-life hardware, restrict the management interface to known IPs and record a dated replacement plan. For end-of-life devices, budget for replacement now. Underwriters rarely accept "we'll get to it next year" for an unsupported edge device.
Looking to streamline vendor RFP selection?
Access pre-negotiated tier discounts through our independent institutional network.
Days 8–15: Fix Email Authentication Without Breaking Legitimate Mail
Email findings usually fall into three groups: a missing or overly permissive SPF record, no DKIM signing, and DMARC set to p=none or absent. Carriers price these because business email compromise and funds-transfer fraud are major claim categories in every region.
Don't jump straight to p=reject. Inventory every service that sends as your domain, including CRM, payroll, ticketing and marketing platforms, then align SPF and DKIM for each. Run DMARC at p=none with reporting for one to two weeks, review the aggregate reports, then move to p=quarantine. For most mid-size companies, quarantine at full enforcement is usually enough to satisfy an underwriter before binding, and you can move to reject after renewal. Don't forget parked and regional domains. If a scan finds your .co.uk, .de or .in domain unprotected, it counts against you.
Days 10–20: Dispute False Positives With Evidence, Not Argument
Attribution errors happen. Typical cases include IP addresses you released months ago, shared hosting or CDN ranges that belong to the provider, a subsidiary you divested, honeypots, and services behind a web application firewall that the scanner misreads.
For each dispute, provide:
- The asset, the finding and a one-line reason it's wrong.
- Proof: a cloud provider or ISP record showing current IP ownership, WHOIS or registrar data, a screenshot of the firewall rule, or a fresh scan result with date and time.
- A named contact who can answer follow-up questions.
Send disputes through your broker in a single batch. Many scanning platforms, including SecurityScorecard and BitSight, offer correction workflows, as do some carrier-run tools. Corrections can take a few weeks, so file early.
Days 15–25: Run Your Own Outside-In Scan Before the Carrier Reruns Theirs
Don't rely on the carrier's rescan to tell you whether a fix worked. A scan you run yourself shows what the underwriter will see. External attack surface management (EASM) tools do this continuously. Some carriers, including Coalition and At-Bay, give policyholders access to their own monitoring platforms, so ask about it during placement.
| Option | Indicative annual cost (USD) | Best fit |
|---|---|---|
| Carrier-provided monitoring | Often bundled with the policy | Small and mid-size firms wanting the carrier's own view |
| Self-serve search engines (Shodan, Censys tiers) | Low hundreds to a few thousand | Teams with in-house technical staff |
| Mid-market rating/EASM platforms (e.g., UpGuard) | Roughly $5,000–$30,000 | Firms with vendor-risk needs as well |
| Enterprise ratings and EASM (SecurityScorecard, BitSight, Microsoft Defender EASM, Palo Alto Cortex Xpanse) | Roughly $20,000–$150,000+ | Large, multi-country estates |
These are typical 2026 market ranges that vary by contract, asset count and region. Confirm pricing with vendors or local resellers.
Days 21–30: Package the Evidence So the Underwriter Can Re-Rate
Underwriters move faster when the file answers their questions without a follow-up call. Build a short remediation pack, typically a few pages:
- A cover memo listing each original finding and its status: fixed, disputed or accepted with mitigation.
- Before-and-after evidence for each fix, with dates.
- Your own clean scan output from the last seven days.
- For any open item, a dated plan with a named owner and the compensating control in place.
- A signed statement from the CISO or IT lead confirming accuracy.
Ask the broker to request a formal rescan and re-rating before binding, not at renewal. Be precise in every statement. Anything you represent in this pack can become part of the application, and misstatements can cause coverage disputes later. Have your broker or counsel review the wording.
Red Flags and a Decision Rule If You Can't Finish in 30 Days
Watch for a quote with a ransomware sublimit or coinsurance tied to specific scan findings, a subjectivity requiring remediation "within 30 days of binding" with no verification process, or a carrier that won't share the underlying findings. Each one shifts risk back onto you.
Market practice varies. Lloyd's and European carriers, US admitted markets, and insurers in Asia-Pacific, the Middle East and Latin America differ in how strictly they apply scan results and whether post-bind subjectivities are allowed. Ask your broker how the specific carrier treats unresolved items.
Use this rule. If exposed remote access or a known-exploited edge device is still open on day 30, accept a short-term bind with a written subjectivity rather than misstate your posture, and close it within two weeks. If only email or low-severity items remain, push for full terms with your dated plan attached. Start today by asking your broker for the raw scan report.