Three scenarios dominate the claims data. First, a compromised vendor email chain leads your AP team to redirect a legitimate invoice payment to a new bank account controlled by a criminal. Second, a spoofed executive email instructs your controller to wire funds for a confidential acquisition or urgent tax payment. Third, a threat actor compromises your company's own email system and intercepts outbound payment instructions to your clients, redirecting incoming payments. Each scenario triggers a different coverage grant, and some policies cover only one or two of the three.
Common Wire Transfer Loss Scenarios
Every year, more enterprise buyers and procurement teams require their vendors to produce a SOC 2 report before signing a contract. That same report is now showing up in cyber insurance applications, too. Underwriters want to see how your controls are designed and whether they actually work, because the answers directly shape your premium, your coverage terms, and whether a policy form will respond when a claim hits. For small and mid-market companies running between 10 and 500 employees, the overlap between SOC 2 compliance and cyber insurance requirements creates real confusion: which Trust Services Criteria matter to insurers, how do Type I and Type II reports differ for eligibility, what happens when your audit has control exceptions, and how should you answer vendor questionnaire items about insurance? This guide walks through each of those questions, connecting SOC 2 audit requirements to the specific places a cyber liability policy responds, so you can close gaps before a breach or a customer contract exposes them.
Understanding the Link Between SOC 2 and Cyber Insurance
SOC 2 reports and cyber insurance applications ask many of the same questions, but for different reasons. The audit evaluates whether your controls meet Trust Services Criteria. The insurer evaluates whether those controls reduce the likelihood and severity of a claim. Where those two evaluations overlap is where underwriting decisions are made: your MFA deployment, endpoint detection, backup procedures, and incident response plans appear in both contexts.
Why Underwriters Require SOC 2 Reports
Underwriters are not auditors, but they read audit reports. A SOC 2 report gives them independent verification that your security controls exist and, in the case of a Type II, that they operated effectively over a defined period. The cyber insurance market is projected to exceed $33 billion by 2028, and that growth is driven partly by carriers demanding better risk data before quoting. A clean SOC 2 report can reduce the number of supplemental questions on an application, accelerate the quoting timeline, and in some cases improve pricing. Carriers are not giving blanket discounts for having a report, but they are penalizing applicants who cannot demonstrate basic control maturity.
The Difference Between Type I and Type II for Insurance Eligibility
A Type I report evaluates the design of your controls at a single point in time. A Type II report evaluates both design and operating effectiveness over a minimum observation period, typically six to twelve months. Most underwriters prefer Type II because it shows that controls were not just designed on paper but actually functioned during the review window. A Type I is not disqualifying, but expect follow-up questions. Carriers may ask for supplemental attestations or require a Type II before renewal if you only submitted a Type I at binding.
By: Caden Braly
Founder of Bloc Cyber Insurance
INDEX
Understanding the Link Between SOC 2 and Cyber Insurance
Mapping Trust Services Criteria to Policy Coverage
Comparison: SOC 2 Compliance vs. Standard Cyber Insurance Requirements
Where a Cyber Policy Responds to SOC 2 Gaps
Navigating Customer Contracts and Vendor Questionnaires
Frequently Asked Questions About SOC 2 and Insurance
How Control Exceptions Affect Policy Terms
Aligning Your SOC 2 Roadmap with Insurance Renewals
The Role of Trust Services Criteria in Claims Outcomes
Vendor Questionnaire Answers That Insurers Actually Verify
Connecting SOC 2 Findings to Cyber Policy Insuring Agreements
Bloc Cyber and Its Licensed Producers Are Authorized to Place Cyber Coverage in All 50 U.S. States and The District of Columbia.
Cyber liability insurance covers the financial losses your business faces after a cyberattack or data breach. This page explains what the coverage includes, who needs it, what it costs, and how Bloc Cyber helps you get protected fast.
We start with a twenty-minute call to walk through your contracts, your draw process, your tech stack, and the last twelve months of attempted fraud. From there we go to market with ten-plus carriers, benchmark terms side-by-side, and present the options in plain language with recommended limits and retentions. Most intakes get indicative terms within one business day.
Forensic Investigations: Identifying the Source and Scope
Forensic investigators determine how the attacker got in, what data was accessed, whether exfiltration occurred, and whether the threat actor is still present in the network. Their report drives every downstream decision: which individuals must be notified, whether payment card brands must be alerted, and what remediation steps are necessary. Forensic engagements for mid-market companies commonly run between $30,000 and $150,000, depending on the complexity of the environment. The policy form may impose a separate sublimit on forensic costs or bundle them under a single breach response aggregate. Bloc Cyber reviews these sublimits at the insuring-agreement level before binding, so clients understand exactly how much forensic coverage they are purchasing and where the cap sits relative to their actual exposure.
Mapping Trust Services Criteria to Policy Coverage
The five Trust Services Criteria, Security, Availability, Processing Integrity, Confidentiality, and Privacy, map to different sections of a cyber liability policy form. Understanding which criteria align with which coverage grants helps you see where a gap in your SOC 2 report could translate to a gap in your insurance program.
Security, Confidentiality, and Privacy Requirements
The Security criterion is foundational. It covers logical access controls, network monitoring, encryption, and incident detection. These controls map directly to the first-party breach response and third-party liability insuring agreements in most cyber policy forms. Confidentiality controls, covering how you protect non-public information, align with the data breach notification and regulatory defense coverage grants. Privacy controls address how you collect, use, and retain personal information, which maps to privacy regulatory proceedings and, in some forms, media liability.
A weak finding in any of these three criteria raises a red flag for underwriters. If your SOC 2 report shows that encryption at rest is not enforced or that access reviews are inconsistent, the carrier may add a sublimit, increase the retention, or exclude a specific coverage section.
Availability and Processing Integrity Controls
Availability controls address system uptime, disaster recovery, and business continuity. These map most directly to business interruption and system failure coverage in a cyber policy. Processing Integrity controls, which ensure that data processing is complete, accurate, and authorized, are relevant to technology errors and omissions coverage. If your platform processes financial transactions or healthcare data and your SOC 2 report flags processing integrity exceptions, a technology E&O insuring agreement may carry a higher retention or a co-insurance clause.
The gap between a basic crime policy and a comprehensive fraud protection program is significant. The table below highlights key differences.
We start with a twenty-minute call to walk through your contracts, your draw process, your tech stack, and the last twelve months of attempted fraud. From there we go to market with ten-plus carriers, benchmark terms side-by-side, and present the options in plain language with recommended limits and retentions. Most intakes get indicative terms within one business day.
This comparison illustrates why a general liability policy, even one with a broad "personal and advertising injury" grant, will not respond to a regulatory proceeding. The coverage must be placed specifically under a cyber or technology E&O form that includes regulatory defense as a named insuring agreement.
| Coverage Feature | Basic Crime Policy | Comprehensive Cyber with Fraud Coverage |
|---|---|---|
| Computer Fraud | Typically included | Included |
| Social Engineering | Optional endorsement, low sublimit | Included, higher sublimits available |
| Push Payment Fraud | Often excluded | May be covered as separate grant |
| Account Takeover | May fall under computer fraud | Explicitly covered |
| Forensic Investigation | Not covered | First-party expense coverage |
| Legal and Regulatory Costs | Not covered | Included |
| Callback Verification Required | Yes, strict condition | Yes, but terms vary by form |
| Typical Sublimit Range | $100K - $250K | $250K - $1M+ |
R&W retentions function similarly to a deductible but are typically structured as a percentage of enterprise value. A common retention for mid-market deals sits between 1% and 3% of the transaction value. On a $50 million deal, that means the buyer absorbs the first $500,000 to $1.5 million of covered losses before the insurer pays anything. The retention exists because underwriters expect the buyer's own diligence to catch smaller issues. Retention levels are negotiable and vary by carrier, deal size, and the quality of the diligence package presented during underwriting.
How Retention Works as a Deductible
The Transition from Retention to Drop-Down Coverage
Most R&W policies include a drop-down feature that reduces the retention, often by half, after a specified period, typically 12 months post-closing. If the original retention is $1 million, it drops to $500,000 after the first year. This mechanism reflects the assumption that the most significant breaches surface early. The reduced retention in the later period provides the buyer with more accessible coverage for claims that emerge after the initial post-closing adjustment period. Some policies offer a full drop to zero retention after 18 or 24 months, though this depends on the specific terms negotiated with the underwriter.
Comparison: SOC 2 Compliance vs. Standard Cyber Insurance Requirements
| Area | SOC 2 Requirement | Typical Cyber Insurance Requirement |
|---|---|---|
| Multi-Factor Authentication | Required under Security criterion for logical access | Required on all remote access, email, and admin consoles |
| Endpoint Detection & Response | Recommended but not always mandated | Frequently required; some carriers mandate specific vendors |
| Encryption | Required for data in transit; recommended at rest | Required for both in transit and at rest on most applications |
| Incident Response Plan | Required under Security criterion | Required; some carriers want to see tabletop exercise records |
| Backup & Recovery | Covered under Availability criterion | Required with tested restoration procedures |
| Vendor Management | Covered under Confidentiality or Security | Asked about in applications; subcontractor liability coverage may depend on it |
| Employee Training | Required under Security criterion | Required; frequency and phishing simulation results often requested |
The table above shows that SOC 2 and cyber insurance requirements overlap heavily, but insurance applications often go further on specific technical controls. A SOC 2 report alone does not satisfy every underwriting question.
We start with a twenty-minute call to walk through your contracts, your draw process, your tech stack, and the last twelve months of attempted fraud. From there we go to market with ten-plus carriers, benchmark terms side-by-side, and present the options in plain language with recommended limits and retentions. Most intakes get indicative terms within one business day.
| Coverage Element | Commercial General Liability | Cyber Insurance |
|---|---|---|
| Data breach notification costs | Not covered | Covered under first-party |
| Ransomware payment | Not covered | Covered (subject to sublimit) |
| Regulatory defense | Not covered | Covered under third-party |
| Business interruption from cyberattack | Not covered | Covered with waiting period |
| Funds transfer fraud | Not covered | Covered via cyber crime endorsement |
| Third-party lawsuit over data loss | Excluded or severely limited | Covered under third-party liability |
| Technology product failure | Not covered | Covered under Tech E&O |
Most states have not passed explicit statutes declaring regulatory fines insurable or uninsurable. Instead, the question turns on public policy: courts in some jurisdictions hold that allowing insurance to pay a punitive or regulatory fine would undermine the fine's deterrent purpose. New York, for example, has case law suggesting that certain regulatory penalties are uninsurable on public policy grounds. Texas and California courts have taken different positions depending on the type of fine and the regulatory scheme involved.
Your policy form will typically include language stating that fines and penalties are covered "to the extent insurable under applicable law." This shifts the jurisdictional analysis to the time of claim. Bloc Cyber maintains state-by-state fluency in breach-notification triggers and regulatory defense exposure, which matters when your operations span multiple states with different public policy positions on fine insurability.
State-by-State Variations in Public Policy and Uninsurable Fines
Companies with operations in the EU, UK, or Asia-Pacific face additional complexity. GDPR fines imposed by European data protection authorities can reach four percent of global annual revenue. Whether a US-placed policy can respond to a GDPR fine depends on the policy's territorial scope, the choice-of-law provisions, and whether the jurisdiction where the fine is imposed permits its insurance.
Many standard cyber forms limit territorial coverage to the United States and its territories. If your company has employees, customers, or data processing activities in Europe, you need a form with international regulatory coverage or a locally admitted policy in the relevant jurisdiction. The cost of getting this wrong is not theoretical: monitor and compliance fees in cross-border enforcement actions can compound rapidly when multiple regulators coordinate investigations.
International Considerations for Multinational Regulatory Risks
Addressing Known Issues and Exclusions
Any issue identified during diligence that is disclosed to the underwriter becomes a known issue and is excluded from coverage. This is a fundamental principle of R&W insurance: it covers unknown breaches, not problems you already know about. Buyers sometimes assume they can disclose a problem and still obtain coverage for it. They cannot. The underwriter will carve out any known matter, and the buyer must negotiate a specific indemnity from the seller or accept the risk. This is where the interplay between your diligence process and your insurance placement becomes critical: thoroughness in diligence improves your coverage, but every issue you find narrows it.
For companies that carry cyber liability or technology E&O policies, this dynamic should feel familiar. At Bloc Cyber, we see a parallel in how cyber insurers evaluate a company's security posture before binding coverage: known vulnerabilities get excluded or trigger higher retentions, just as known issues do in R&W underwriting.
How much does cyber insurance cost for a small firm?
A firm of 10 to 25 attorneys can typically expect premiums in the range of $3,000 to $12,000 annually for $1 million in coverage, depending on practice areas, security controls in place, and claims history. Firms handling real estate closings or M&A work will pay more because of the wire-fraud exposure.
Where a Cyber Policy Responds to SOC 2 Gaps
Your SOC 2 report documents what your controls look like. Your cyber policy form defines what happens financially when those controls fail. A first-party breach response grant typically covers forensic investigation, legal counsel, notification costs, and credit monitoring. A third-party liability grant covers defense costs and settlements arising from claims by affected individuals or businesses. Technology E&O coverage responds when a failure in your product or service causes financial harm to a client.
The critical question is whether the policy form covers the specific failure mode your SOC 2 report flagged. If your report noted an exception in access management and an attacker later exploited that exact weakness, the carrier's claims team will review whether the application was answered accurately. Misrepresentation on an application can void coverage entirely, which is why aligning your SOC 2 findings with your insurance application answers is not optional.
We start with a twenty-minute call to walk through your contracts, your draw process, your tech stack, and the last twelve months of attempted fraud. From there we go to market with ten-plus carriers, benchmark terms side-by-side, and present the options in plain language with recommended limits and retentions. Most intakes get indicative terms within one business day.
FAQ: Does my general business insurance cover hacking?
Almost certainly not. Standard CGL and BOP policies contain electronic data exclusions. Even if your policy has a small "data breach" endorsement, it is typically capped at $50,000 to $100,000, which will not cover a meaningful incident. A standalone cyber liability form provides the breadth and limits required for a real claim.
FAQ: How does a consent order affect my future premiums?
A consent order signals increased risk to underwriters. Expect premium increases at renewal, potentially 25 to 100 percent or more depending on the severity of the order and your compliance track record. Some carriers may decline to renew entirely if the consent order reveals systemic compliance failures.
Law firm cyber coverage is not a commodity product you can purchase by checking a box on a general liability application. The risks are specific: trust account fraud, privileged document exposure, deal data theft, multi-state notification obligations, and business interruption measured in lost billable hours. Your policy needs to reflect those risks at the insuring-agreement level, with sub-limits and retentions that match your actual exposure.
Do not wait for a breach to discover that your social engineering sub-limit is $100,000 on a $1.2 million wire or that your business-interruption waiting period is 24 hours when your systems were down for a week. If you are purchasing your first cyber policy or renewing an existing one, have a specialist review the actual policy form with you. Bloc Cyber's practice is built entirely around cyber, technology E&O, and AI liability placement. You can
request a coverage review to have a specialist walk through the insuring agreements, sub-limits, and exclusions specific to your firm's risk profile before you bind.
Navigating Customer Contracts and Vendor Questionnaires
Enterprise customers increasingly require both a SOC 2 report and proof of cyber insurance before executing a contract. These two requirements are connected: the SOC 2 report tells the customer how you protect their data, and the insurance certificate tells them who pays when something goes wrong.
Common Insurance Clauses in SaaS Agreements
SaaS contracts frequently include minimum insurance requirements: $1 million to $5 million in cyber liability, sometimes with technology E&O included. Many contracts also require that the vendor name the customer as an additional insured or provide a waiver of subrogation. Before agreeing to these terms, review your policy form carefully. Not every cyber policy allows additional insured status, and waiver of subrogation endorsements may carry conditions. At Bloc Cyber, we review these contract clauses against the actual policy language before binding, because a certificate of insurance that does not match the contract terms creates a false sense of security for both parties.
Handling Control Exceptions in Audit Reports
Control exceptions in a SOC 2 report are not automatic disqualifiers for insurance. What matters is how you respond to them. Underwriters want to see a remediation plan with specific timelines. If your report includes three exceptions but you can show that two are already remediated and the third has a compensating control in place, most carriers will still quote. The problem arises when exceptions are left unaddressed across multiple audit periods. That pattern signals to underwriters that management does not treat the findings seriously, and it will affect both pricing and coverage terms.
Passing the Cyber Insurance Vendor Risk Assessment
Many carriers now use standardized vendor risk assessments that mirror SOC 2 control categories. Your SOC 2 report can serve as supporting documentation for these assessments, but you will still need to answer application questions directly. Common areas where applicants stumble include: failing to disclose prior incidents, overstating the scope of MFA deployment, and mischaracterizing backup testing frequency. Answer every question based on your current state, not your planned state. If your SOC 2 report says one thing and your application says another, the discrepancy will surface during a claim.
We start with a twenty-minute call to walk through your contracts, your draw process, your tech stack, and the last twelve months of attempted fraud. From there we go to market with ten-plus carriers, benchmark terms side-by-side, and present the options in plain language with recommended limits and retentions. Most intakes get indicative terms within one business day.
| Coverage Element | Commercial General Liability | Cyber Insurance |
|---|---|---|
| Data breach notification costs | Not covered | Covered under first-party |
| Ransomware payment | Not covered | Covered (subject to sublimit) |
| Regulatory defense | Not covered | Covered under third-party |
| Business interruption from cyberattack | Not covered | Covered with waiting period |
| Funds transfer fraud | Not covered | Covered via cyber crime endorsement |
| Third-party lawsuit over data loss | Excluded or severely limited | Covered under third-party liability |
| Technology product failure | Not covered | Covered under Tech E&O |
Most states have not passed explicit statutes declaring regulatory fines insurable or uninsurable. Instead, the question turns on public policy: courts in some jurisdictions hold that allowing insurance to pay a punitive or regulatory fine would undermine the fine's deterrent purpose. New York, for example, has case law suggesting that certain regulatory penalties are uninsurable on public policy grounds. Texas and California courts have taken different positions depending on the type of fine and the regulatory scheme involved.
Your policy form will typically include language stating that fines and penalties are covered "to the extent insurable under applicable law." This shifts the jurisdictional analysis to the time of claim. Bloc Cyber maintains state-by-state fluency in breach-notification triggers and regulatory defense exposure, which matters when your operations span multiple states with different public policy positions on fine insurability.
State-by-State Variations in Public Policy and Uninsurable Fines
Companies with operations in the EU, UK, or Asia-Pacific face additional complexity. GDPR fines imposed by European data protection authorities can reach four percent of global annual revenue. Whether a US-placed policy can respond to a GDPR fine depends on the policy's territorial scope, the choice-of-law provisions, and whether the jurisdiction where the fine is imposed permits its insurance.
Many standard cyber forms limit territorial coverage to the United States and its territories. If your company has employees, customers, or data processing activities in Europe, you need a form with international regulatory coverage or a locally admitted policy in the relevant jurisdiction. The cost of getting this wrong is not theoretical: monitor and compliance fees in cross-border enforcement actions can compound rapidly when multiple regulators coordinate investigations.
International Considerations for Multinational Regulatory Risks
Addressing Known Issues and Exclusions
Any issue identified during diligence that is disclosed to the underwriter becomes a known issue and is excluded from coverage. This is a fundamental principle of R&W insurance: it covers unknown breaches, not problems you already know about. Buyers sometimes assume they can disclose a problem and still obtain coverage for it. They cannot. The underwriter will carve out any known matter, and the buyer must negotiate a specific indemnity from the seller or accept the risk. This is where the interplay between your diligence process and your insurance placement becomes critical: thoroughness in diligence improves your coverage, but every issue you find narrows it.
For companies that carry cyber liability or technology E&O policies, this dynamic should feel familiar. At Bloc Cyber, we see a parallel in how cyber insurers evaluate a company's security posture before binding coverage: known vulnerabilities get excluded or trigger higher retentions, just as known issues do in R&W underwriting.
Post-Incident Forensic and Legal Obligations
After a SCADA or OT intrusion, you will likely face parallel investigations: your own internal forensic team, your insurer's panel forensics firm, CISA, and potentially your state public utility commission. A coordinated attack on Minnesota water utilities demonstrated how quickly a regional incident can trigger multi-agency scrutiny.
Your policy should not restrict your choice of forensic investigators to a panel that lacks OT expertise. If the form requires you to use a pre-approved vendor, confirm that vendor has ICS forensic capability. The wrong forensic team can miss artifacts specific to industrial protocols like Modbus or DNP3, leaving you with an incomplete investigation and a disputed claim.
How much does cyber insurance cost for a small firm?
A firm of 10 to 25 attorneys can typically expect premiums in the range of $3,000 to $12,000 annually for $1 million in coverage, depending on practice areas, security controls in place, and claims history. Firms handling real estate closings or M&A work will pay more because of the wire-fraud exposure.
Frequently Asked Questions About SOC 2 and Insurance
Does a SOC 2 report guarantee lower cyber insurance premiums? No. A clean Type II report may improve your risk profile and lead to more favorable terms, but premiums depend on revenue, industry, claims history, and the specific controls you have in place.
Can I get cyber insurance without a SOC 2 report? Yes. SOC 2 is not a prerequisite for all cyber policies. Carriers will still underwrite based on your application answers and supplemental security questionnaires.
What happens if my SOC 2 report has exceptions? Exceptions do not automatically prevent you from obtaining coverage. Carriers evaluate whether exceptions are material, whether remediation plans exist, and whether compensating controls are in place.
Do I need both Type I and Type II reports? Not typically. A Type II report supersedes a Type I. If you are early in your SOC 2 journey, a Type I can serve as a bridge, but plan to move to Type II within 12 months.
Should my cyber policy limits match what my customer contracts require? Your policy limits should reflect both your contractual obligations and your actual risk exposure. A contract may require $5 million, but your risk profile might warrant higher or lower limits depending on the data you handle.
We start with a twenty-minute call to walk through your contracts, your draw process, your tech stack, and the last twelve months of attempted fraud. From there we go to market with ten-plus carriers, benchmark terms side-by-side, and present the options in plain language with recommended limits and retentions. Most intakes get indicative terms within one business day.
FAQ: Does my general business insurance cover hacking?
Almost certainly not. Standard CGL and BOP policies contain electronic data exclusions. Even if your policy has a small "data breach" endorsement, it is typically capped at $50,000 to $100,000, which will not cover a meaningful incident. A standalone cyber liability form provides the breadth and limits required for a real claim.
FAQ: How does a consent order affect my future premiums?
A consent order signals increased risk to underwriters. Expect premium increases at renewal, potentially 25 to 100 percent or more depending on the severity of the order and your compliance track record. Some carriers may decline to renew entirely if the consent order reveals systemic compliance failures.
Law firm cyber coverage is not a commodity product you can purchase by checking a box on a general liability application. The risks are specific: trust account fraud, privileged document exposure, deal data theft, multi-state notification obligations, and business interruption measured in lost billable hours. Your policy needs to reflect those risks at the insuring-agreement level, with sub-limits and retentions that match your actual exposure.
Do not wait for a breach to discover that your social engineering sub-limit is $100,000 on a $1.2 million wire or that your business-interruption waiting period is 24 hours when your systems were down for a week. If you are purchasing your first cyber policy or renewing an existing one, have a specialist review the actual policy form with you. Bloc Cyber's practice is built entirely around cyber, technology E&O, and AI liability placement. You can
request a coverage review to have a specialist walk through the insuring agreements, sub-limits, and exclusions specific to your firm's risk profile before you bind.
Control exceptions in a SOC 2 report are not automatic disqualifiers for insurance. What matters is how you respond to them. Underwriters want to see a remediation plan with specific timelines. If your report includes three exceptions but you can show that two are already remediated and the third has a compensating control in place, most carriers will still quote. The problem arises when exceptions are left unaddressed across multiple audit periods. That pattern signals to underwriters that management does not treat the findings seriously, and it will affect both pricing and coverage terms.
Handling Control Exceptions in Audit Reports
Passing the Cyber Insurance Vendor Risk Assessment
Many carriers now use standardized vendor risk assessments that mirror SOC 2 control categories. Your SOC 2 report can serve as supporting documentation for these assessments, but you will still need to answer application questions directly. Common areas where applicants stumble include: failing to disclose prior incidents, overstating the scope of MFA deployment, and mischaracterizing backup testing frequency. Answer every question based on your current state, not your planned state. If your SOC 2 report says one thing and your application says another, the discrepancy will surface during a claim.
How Control Exceptions Affect Policy Terms
A single control exception rarely changes your policy terms. A pattern of unresolved exceptions across audit cycles will. Carriers may respond by adding exclusions for specific incident types, increasing retentions on breach response coverage, or imposing sublimits on regulatory defense costs. The fix is straightforward: treat your SOC 2 remediation plan as an insurance requirement, not just an audit deliverable.
We start with a twenty-minute call to walk through your contracts, your draw process, your tech stack, and the last twelve months of attempted fraud. From there we go to market with ten-plus carriers, benchmark terms side-by-side, and present the options in plain language with recommended limits and retentions. Most intakes get indicative terms within one business day.
| Coverage Element | Commercial General Liability | Cyber Insurance |
|---|---|---|
| Data breach notification costs | Not covered | Covered under first-party |
| Ransomware payment | Not covered | Covered (subject to sublimit) |
| Regulatory defense | Not covered | Covered under third-party |
| Business interruption from cyberattack | Not covered | Covered with waiting period |
| Funds transfer fraud | Not covered | Covered via cyber crime endorsement |
| Third-party lawsuit over data loss | Excluded or severely limited | Covered under third-party liability |
| Technology product failure | Not covered | Covered under Tech E&O |
Most states have not passed explicit statutes declaring regulatory fines insurable or uninsurable. Instead, the question turns on public policy: courts in some jurisdictions hold that allowing insurance to pay a punitive or regulatory fine would undermine the fine's deterrent purpose. New York, for example, has case law suggesting that certain regulatory penalties are uninsurable on public policy grounds. Texas and California courts have taken different positions depending on the type of fine and the regulatory scheme involved.
Your policy form will typically include language stating that fines and penalties are covered "to the extent insurable under applicable law." This shifts the jurisdictional analysis to the time of claim. Bloc Cyber maintains state-by-state fluency in breach-notification triggers and regulatory defense exposure, which matters when your operations span multiple states with different public policy positions on fine insurability.
State-by-State Variations in Public Policy and Uninsurable Fines
Companies with operations in the EU, UK, or Asia-Pacific face additional complexity. GDPR fines imposed by European data protection authorities can reach four percent of global annual revenue. Whether a US-placed policy can respond to a GDPR fine depends on the policy's territorial scope, the choice-of-law provisions, and whether the jurisdiction where the fine is imposed permits its insurance.
Many standard cyber forms limit territorial coverage to the United States and its territories. If your company has employees, customers, or data processing activities in Europe, you need a form with international regulatory coverage or a locally admitted policy in the relevant jurisdiction. The cost of getting this wrong is not theoretical: monitor and compliance fees in cross-border enforcement actions can compound rapidly when multiple regulators coordinate investigations.
International Considerations for Multinational Regulatory Risks
Addressing Known Issues and Exclusions
Any issue identified during diligence that is disclosed to the underwriter becomes a known issue and is excluded from coverage. This is a fundamental principle of R&W insurance: it covers unknown breaches, not problems you already know about. Buyers sometimes assume they can disclose a problem and still obtain coverage for it. They cannot. The underwriter will carve out any known matter, and the buyer must negotiate a specific indemnity from the seller or accept the risk. This is where the interplay between your diligence process and your insurance placement becomes critical: thoroughness in diligence improves your coverage, but every issue you find narrows it.
For companies that carry cyber liability or technology E&O policies, this dynamic should feel familiar. At Bloc Cyber, we see a parallel in how cyber insurers evaluate a company's security posture before binding coverage: known vulnerabilities get excluded or trigger higher retentions, just as known issues do in R&W underwriting.
Post-Incident Forensic and Legal Obligations
After a SCADA or OT intrusion, you will likely face parallel investigations: your own internal forensic team, your insurer's panel forensics firm, CISA, and potentially your state public utility commission. A coordinated attack on Minnesota water utilities demonstrated how quickly a regional incident can trigger multi-agency scrutiny.
Your policy should not restrict your choice of forensic investigators to a panel that lacks OT expertise. If the form requires you to use a pre-approved vendor, confirm that vendor has ICS forensic capability. The wrong forensic team can miss artifacts specific to industrial protocols like Modbus or DNP3, leaving you with an incomplete investigation and a disputed claim.
How much does cyber insurance cost for a small firm?
A firm of 10 to 25 attorneys can typically expect premiums in the range of $3,000 to $12,000 annually for $1 million in coverage, depending on practice areas, security controls in place, and claims history. Firms handling real estate closings or M&A work will pay more because of the wire-fraud exposure.
Aligning Your SOC 2 Roadmap with Insurance Renewals
Time your SOC 2 audit cycle so that your Type II report is available before your cyber insurance renewal. A report issued three months before renewal gives your broker time to present it to multiple carriers and negotiate terms. If your report lands after the renewal date, you miss the window to use it as underwriting evidence until the following year.
We start with a twenty-minute call to walk through your contracts, your draw process, your tech stack, and the last twelve months of attempted fraud. From there we go to market with ten-plus carriers, benchmark terms side-by-side, and present the options in plain language with recommended limits and retentions. Most intakes get indicative terms within one business day.
FAQ: Does my general business insurance cover hacking?
Almost certainly not. Standard CGL and BOP policies contain electronic data exclusions. Even if your policy has a small "data breach" endorsement, it is typically capped at $50,000 to $100,000, which will not cover a meaningful incident. A standalone cyber liability form provides the breadth and limits required for a real claim.
FAQ: How does a consent order affect my future premiums?
A consent order signals increased risk to underwriters. Expect premium increases at renewal, potentially 25 to 100 percent or more depending on the severity of the order and your compliance track record. Some carriers may decline to renew entirely if the consent order reveals systemic compliance failures.
Law firm cyber coverage is not a commodity product you can purchase by checking a box on a general liability application. The risks are specific: trust account fraud, privileged document exposure, deal data theft, multi-state notification obligations, and business interruption measured in lost billable hours. Your policy needs to reflect those risks at the insuring-agreement level, with sub-limits and retentions that match your actual exposure.
Do not wait for a breach to discover that your social engineering sub-limit is $100,000 on a $1.2 million wire or that your business-interruption waiting period is 24 hours when your systems were down for a week. If you are purchasing your first cyber policy or renewing an existing one, have a specialist review the actual policy form with you. Bloc Cyber's practice is built entirely around cyber, technology E&O, and AI liability placement. You can
request a coverage review to have a specialist walk through the insuring agreements, sub-limits, and exclusions specific to your firm's risk profile before you bind.
Control exceptions in a SOC 2 report are not automatic disqualifiers for insurance. What matters is how you respond to them. Underwriters want to see a remediation plan with specific timelines. If your report includes three exceptions but you can show that two are already remediated and the third has a compensating control in place, most carriers will still quote. The problem arises when exceptions are left unaddressed across multiple audit periods. That pattern signals to underwriters that management does not treat the findings seriously, and it will affect both pricing and coverage terms.
Handling Control Exceptions in Audit Reports
Passing the Cyber Insurance Vendor Risk Assessment
Many carriers now use standardized vendor risk assessments that mirror SOC 2 control categories. Your SOC 2 report can serve as supporting documentation for these assessments, but you will still need to answer application questions directly. Common areas where applicants stumble include: failing to disclose prior incidents, overstating the scope of MFA deployment, and mischaracterizing backup testing frequency. Answer every question based on your current state, not your planned state. If your SOC 2 report says one thing and your application says another, the discrepancy will surface during a claim.
The Role of Trust Services Criteria in Claims Outcomes
When a claim is filed, the carrier's claims team reviews the policy form, the application, and any supporting documentation, including your SOC 2 report. If your report demonstrates that controls were operating effectively at the time of the incident, it strengthens your position. If the report shows a known gap that was not disclosed on the application, it weakens it. The SOC 2 report becomes part of the factual record during claims adjustment.
We start with a twenty-minute call to walk through your contracts, your draw process, your tech stack, and the last twelve months of attempted fraud. From there we go to market with ten-plus carriers, benchmark terms side-by-side, and present the options in plain language with recommended limits and retentions. Most intakes get indicative terms within one business day.
| Coverage Element | Commercial General Liability | Cyber Insurance |
|---|---|---|
| Data breach notification costs | Not covered | Covered under first-party |
| Ransomware payment | Not covered | Covered (subject to sublimit) |
| Regulatory defense | Not covered | Covered under third-party |
| Business interruption from cyberattack | Not covered | Covered with waiting period |
| Funds transfer fraud | Not covered | Covered via cyber crime endorsement |
| Third-party lawsuit over data loss | Excluded or severely limited | Covered under third-party liability |
| Technology product failure | Not covered | Covered under Tech E&O |
Most states have not passed explicit statutes declaring regulatory fines insurable or uninsurable. Instead, the question turns on public policy: courts in some jurisdictions hold that allowing insurance to pay a punitive or regulatory fine would undermine the fine's deterrent purpose. New York, for example, has case law suggesting that certain regulatory penalties are uninsurable on public policy grounds. Texas and California courts have taken different positions depending on the type of fine and the regulatory scheme involved.
Your policy form will typically include language stating that fines and penalties are covered "to the extent insurable under applicable law." This shifts the jurisdictional analysis to the time of claim. Bloc Cyber maintains state-by-state fluency in breach-notification triggers and regulatory defense exposure, which matters when your operations span multiple states with different public policy positions on fine insurability.
State-by-State Variations in Public Policy and Uninsurable Fines
Companies with operations in the EU, UK, or Asia-Pacific face additional complexity. GDPR fines imposed by European data protection authorities can reach four percent of global annual revenue. Whether a US-placed policy can respond to a GDPR fine depends on the policy's territorial scope, the choice-of-law provisions, and whether the jurisdiction where the fine is imposed permits its insurance.
Many standard cyber forms limit territorial coverage to the United States and its territories. If your company has employees, customers, or data processing activities in Europe, you need a form with international regulatory coverage or a locally admitted policy in the relevant jurisdiction. The cost of getting this wrong is not theoretical: monitor and compliance fees in cross-border enforcement actions can compound rapidly when multiple regulators coordinate investigations.
International Considerations for Multinational Regulatory Risks
Addressing Known Issues and Exclusions
Any issue identified during diligence that is disclosed to the underwriter becomes a known issue and is excluded from coverage. This is a fundamental principle of R&W insurance: it covers unknown breaches, not problems you already know about. Buyers sometimes assume they can disclose a problem and still obtain coverage for it. They cannot. The underwriter will carve out any known matter, and the buyer must negotiate a specific indemnity from the seller or accept the risk. This is where the interplay between your diligence process and your insurance placement becomes critical: thoroughness in diligence improves your coverage, but every issue you find narrows it.
For companies that carry cyber liability or technology E&O policies, this dynamic should feel familiar. At Bloc Cyber, we see a parallel in how cyber insurers evaluate a company's security posture before binding coverage: known vulnerabilities get excluded or trigger higher retentions, just as known issues do in R&W underwriting.
Post-Incident Forensic and Legal Obligations
After a SCADA or OT intrusion, you will likely face parallel investigations: your own internal forensic team, your insurer's panel forensics firm, CISA, and potentially your state public utility commission. A coordinated attack on Minnesota water utilities demonstrated how quickly a regional incident can trigger multi-agency scrutiny.
Your policy should not restrict your choice of forensic investigators to a panel that lacks OT expertise. If the form requires you to use a pre-approved vendor, confirm that vendor has ICS forensic capability. The wrong forensic team can miss artifacts specific to industrial protocols like Modbus or DNP3, leaving you with an incomplete investigation and a disputed claim.
How much does cyber insurance cost for a small firm?
A firm of 10 to 25 attorneys can typically expect premiums in the range of $3,000 to $12,000 annually for $1 million in coverage, depending on practice areas, security controls in place, and claims history. Firms handling real estate closings or M&A work will pay more because of the wire-fraud exposure.
Vendor Questionnaire Answers That Insurers Actually Verify
Carriers increasingly cross-reference application answers with external scanning tools and third-party risk ratings. They check whether your publicly facing infrastructure matches what you disclosed about patching cadence, open ports, and certificate management. Your SOC 2 report should be consistent with these external findings. If your report says you patch critical vulnerabilities within 72 hours but an external scan shows unpatched systems, expect questions during underwriting or, worse, during a claim.
We start with a twenty-minute call to walk through your contracts, your draw process, your tech stack, and the last twelve months of attempted fraud. From there we go to market with ten-plus carriers, benchmark terms side-by-side, and present the options in plain language with recommended limits and retentions. Most intakes get indicative terms within one business day.
FAQ: Does my general business insurance cover hacking?
Almost certainly not. Standard CGL and BOP policies contain electronic data exclusions. Even if your policy has a small "data breach" endorsement, it is typically capped at $50,000 to $100,000, which will not cover a meaningful incident. A standalone cyber liability form provides the breadth and limits required for a real claim.
FAQ: How does a consent order affect my future premiums?
A consent order signals increased risk to underwriters. Expect premium increases at renewal, potentially 25 to 100 percent or more depending on the severity of the order and your compliance track record. Some carriers may decline to renew entirely if the consent order reveals systemic compliance failures.
Law firm cyber coverage is not a commodity product you can purchase by checking a box on a general liability application. The risks are specific: trust account fraud, privileged document exposure, deal data theft, multi-state notification obligations, and business interruption measured in lost billable hours. Your policy needs to reflect those risks at the insuring-agreement level, with sub-limits and retentions that match your actual exposure.
Do not wait for a breach to discover that your social engineering sub-limit is $100,000 on a $1.2 million wire or that your business-interruption waiting period is 24 hours when your systems were down for a week. If you are purchasing your first cyber policy or renewing an existing one, have a specialist review the actual policy form with you. Bloc Cyber's practice is built entirely around cyber, technology E&O, and AI liability placement. You can
request a coverage review to have a specialist walk through the insuring agreements, sub-limits, and exclusions specific to your firm's risk profile before you bind.
Control exceptions in a SOC 2 report are not automatic disqualifiers for insurance. What matters is how you respond to them. Underwriters want to see a remediation plan with specific timelines. If your report includes three exceptions but you can show that two are already remediated and the third has a compensating control in place, most carriers will still quote. The problem arises when exceptions are left unaddressed across multiple audit periods. That pattern signals to underwriters that management does not treat the findings seriously, and it will affect both pricing and coverage terms.
Handling Control Exceptions in Audit Reports
Passing the Cyber Insurance Vendor Risk Assessment
Many carriers now use standardized vendor risk assessments that mirror SOC 2 control categories. Your SOC 2 report can serve as supporting documentation for these assessments, but you will still need to answer application questions directly. Common areas where applicants stumble include: failing to disclose prior incidents, overstating the scope of MFA deployment, and mischaracterizing backup testing frequency. Answer every question based on your current state, not your planned state. If your SOC 2 report says one thing and your application says another, the discrepancy will surface during a claim.
Connecting SOC 2 Findings to Cyber Policy Insuring Agreements
Each insuring agreement in a cyber policy form responds to a specific type of loss. Breach response covers first-party costs. Network security liability covers third-party claims arising from a security failure. Regulatory defense covers fines, penalties, and investigation costs. Technology E&O covers claims arising from your product or service failing to perform. Your SOC 2 report touches all of these areas. The question is whether the controls documented in your report are strong enough to satisfy the conditions precedent in the policy form, and whether your application accurately reflects the state of those controls.
We start with a twenty-minute call to walk through your contracts, your draw process, your tech stack, and the last twelve months of attempted fraud. From there we go to market with ten-plus carriers, benchmark terms side-by-side, and present the options in plain language with recommended limits and retentions. Most intakes get indicative terms within one business day.
| Coverage Element | Commercial General Liability | Cyber Insurance |
|---|---|---|
| Data breach notification costs | Not covered | Covered under first-party |
| Ransomware payment | Not covered | Covered (subject to sublimit) |
| Regulatory defense | Not covered | Covered under third-party |
| Business interruption from cyberattack | Not covered | Covered with waiting period |
| Funds transfer fraud | Not covered | Covered via cyber crime endorsement |
| Third-party lawsuit over data loss | Excluded or severely limited | Covered under third-party liability |
| Technology product failure | Not covered | Covered under Tech E&O |
Most states have not passed explicit statutes declaring regulatory fines insurable or uninsurable. Instead, the question turns on public policy: courts in some jurisdictions hold that allowing insurance to pay a punitive or regulatory fine would undermine the fine's deterrent purpose. New York, for example, has case law suggesting that certain regulatory penalties are uninsurable on public policy grounds. Texas and California courts have taken different positions depending on the type of fine and the regulatory scheme involved.
Your policy form will typically include language stating that fines and penalties are covered "to the extent insurable under applicable law." This shifts the jurisdictional analysis to the time of claim. Bloc Cyber maintains state-by-state fluency in breach-notification triggers and regulatory defense exposure, which matters when your operations span multiple states with different public policy positions on fine insurability.
State-by-State Variations in Public Policy and Uninsurable Fines
Companies with operations in the EU, UK, or Asia-Pacific face additional complexity. GDPR fines imposed by European data protection authorities can reach four percent of global annual revenue. Whether a US-placed policy can respond to a GDPR fine depends on the policy's territorial scope, the choice-of-law provisions, and whether the jurisdiction where the fine is imposed permits its insurance.
Many standard cyber forms limit territorial coverage to the United States and its territories. If your company has employees, customers, or data processing activities in Europe, you need a form with international regulatory coverage or a locally admitted policy in the relevant jurisdiction. The cost of getting this wrong is not theoretical: monitor and compliance fees in cross-border enforcement actions can compound rapidly when multiple regulators coordinate investigations.
International Considerations for Multinational Regulatory Risks
Addressing Known Issues and Exclusions
Any issue identified during diligence that is disclosed to the underwriter becomes a known issue and is excluded from coverage. This is a fundamental principle of R&W insurance: it covers unknown breaches, not problems you already know about. Buyers sometimes assume they can disclose a problem and still obtain coverage for it. They cannot. The underwriter will carve out any known matter, and the buyer must negotiate a specific indemnity from the seller or accept the risk. This is where the interplay between your diligence process and your insurance placement becomes critical: thoroughness in diligence improves your coverage, but every issue you find narrows it.
For companies that carry cyber liability or technology E&O policies, this dynamic should feel familiar. At Bloc Cyber, we see a parallel in how cyber insurers evaluate a company's security posture before binding coverage: known vulnerabilities get excluded or trigger higher retentions, just as known issues do in R&W underwriting.
Post-Incident Forensic and Legal Obligations
After a SCADA or OT intrusion, you will likely face parallel investigations: your own internal forensic team, your insurer's panel forensics firm, CISA, and potentially your state public utility commission. A coordinated attack on Minnesota water utilities demonstrated how quickly a regional incident can trigger multi-agency scrutiny.
Your policy should not restrict your choice of forensic investigators to a panel that lacks OT expertise. If the form requires you to use a pre-approved vendor, confirm that vendor has ICS forensic capability. The wrong forensic team can miss artifacts specific to industrial protocols like Modbus or DNP3, leaving you with an incomplete investigation and a disputed claim.
How much does cyber insurance cost for a small firm?
A firm of 10 to 25 attorneys can typically expect premiums in the range of $3,000 to $12,000 annually for $1 million in coverage, depending on practice areas, security controls in place, and claims history. Firms handling real estate closings or M&A work will pay more because of the wire-fraud exposure.
What This Means for Your Business
SOC 2 compliance and cyber insurance are not separate projects. They share the same underlying question: are your controls strong enough to prevent a loss, and what happens financially if they are not? Your SOC 2 report is underwriting evidence. Your cyber policy form is the financial backstop. The two need to tell the same story.
For companies between 10 and 500 employees, the practical step is to align your audit cycle with your insurance renewal, address control exceptions before they appear on consecutive reports, and answer every application question based on your actual control environment. If your customer contracts require specific insurance terms, verify those terms against your policy form before signing.
If you are preparing for a SOC 2 audit or approaching a cyber insurance renewal, a form-level review of your policy can identify gaps before a claim does. Request a coverage review with a specialist who reads the insuring agreements, endorsements, and exclusions line by line, so you know exactly where the policy responds and where it stops.
ABOUT THE AUTHOR
Caden Braly
— Founder, Bloc Cyber
I'm Caden Braly, founder of Bloc Cyber, the specialty cyber insurance arm of Braly Insurance. I built Bloc Cyber around one idea: businesses deserve coverage that actually responds when a cyberattack happens. I work closely with clients to understand their exposure, place the right policy through specialty carriers, and stand with them through the claim. My goal is simple — give every business straight answers and protection they can trust.
Full profile → caden@bloccyber.com LinkedIn
Industries We Protect
Cyber Coverage Built for Your Industry
Every industry faces a different cyber threat, from patient records in healthcare to wire fraud in construction. Bloc Cyber matches coverage to the risks your sector actually faces, drawing on specialty carriers that understand your business. Find your industry below to see how we protect it.
Healthcare
Banking
Retail / E-Commerce
Legal
Technology / SaaS
Education
Energy / Utilities
Manufacturing
Construction
Defense
Healthcare
HIPAA-grade protection for patient data
725
healthcare breaches disclosed in 2024
HIPAA-grade protection for patient data
▣ Ransomware on EHR systems
▣ PHI exfiltration
▣ Medical device exploits
▣ Business email compromise
Sub-sectors we place
Hospitals and health systems
Physician practices and specialty clinics
Dental practices and DSOs
Behavioral health and addiction treatment centers
Medical billing and revenue cycle management firms
Typical turnaround for indication of terms: 1 business day.
Banking
Coverage that meets FFIEC and NYDFS expectations
$5.9M
average cost of a financial sector breach
Common threats we underwrite against
▣ Wire fraud and BEC
▣ Credential stuffing
▣ Third-party vendor risk
▣ Ransomware
Sub-sectors we place
Community banks
Credit unions
Mortgage lenders and loan originators
Wealth management and RIAs
Payment processors and merchant acquirers
Typical turnaround for indication of terms: 1 business day.
Retail / E-Commerce
PCI-DSS aligned coverage for every checkout
42%
of retailers hit by ransomware in the last year
Common threats we underwrite against
▣ Magecart / card skimming
▣ POS malware
▣ Account takeover
▣ Supply-chain intrusion
Sub-sectors we place
Direct-to-consumer (DTC) brands
Shopify and marketplace sellers
Brick-and-mortar multi-location retailers
Restaurants and QSR franchises
Grocery and specialty food retail
Typical turnaround for indication of terms: 1 business day.
Legal
Privilege, client files, and trust-account safeguards
1 in 4
law firms reported a breach in 2024
Common threats we underwrite against
▣ Wire-transfer fraud
▣ Privileged data theft
▣ Email account compromise
▣ Ransomware
Sub-sectors we place
AmLaw / large firms
Boutique litigation firms
Personal injury and plaintiffs’ firms
Estate planning and trust attorneys
Title and real estate closing firms
Typical turnaround for indication of terms: 1 business day.
Technology / SaaS
SOC 2 and ISO-aligned risk transfer
$4.88M
avg. cost of a SaaS breach in 2024
Common threats we underwrite against
▣ Supply-chain attacks
▣ Cloud misconfiguration
▣ Token and key theft
▣ Zero-day exploits
Sub-sectors we place
B2B SaaS platforms
Managed service providers (MSPs) and MSSPs
Fintech startups
AI and machine learning companies
Cloud hosting and infrastructure providers
Typical turnaround for indication of terms: 1 business day.
Education
FERPA-aligned coverage for student and research data
80%
of K–12 districts hit by ransomware since 2022
Common threats we underwrite against
▣ Ransomware on district networks
▣ Student PII theft
▣ Fake invoice fraud
▣ DDoS on exam platforms
Sub-sectors we place
K-12 public school districts
Private and charter schools
Colleges and universities
EdTech platforms
Tutoring, test prep, and online learning providers
Typical turnaround for indication of terms: 1 business day.
Energy / Utilities
OT and IT coverage for critical infrastructure
24/7
operational-tech monitoring requirements
Common threats we underwrite against
▣ ICS/SCADA intrusion
▣ Nation-state actors
▣ Ransomware on OT
▣ Insider threat
Sub-sectors we place
Municipal utilities (water, electric, gas)
Oil and gas operators
Pipeline and midstream companies
Renewable energy (solar, wind) developers
Electric cooperatives and rural utilities
Typical turnaround for indication of terms: 1 business day.
Manufacturing
Business interruption protection for connected plants
25%
of all ransomware attacks target manufacturing
Common threats we underwrite against
▣ Ransomware halting production
▣ IP theft
▣ ICS exploits
▣ Vendor compromise
Sub-sectors we place
Industrial and heavy equipment manufacturers
Food and beverage processing
Pharmaceutical and medical device manufacturers
Automotive and parts suppliers
Aerospace component manufacturers
Typical turnaround for indication of terms: 1 business day.
Construction
Protection for project files, wires, and jobsite tech
$200K+
average wire-fraud loss in construction
Common threats we underwrite against
▣ Wire-transfer diversion
▣ BEC on project payments
▣ Stolen bid data
▣ Ransomware
Sub-sectors we place
General contractors
Commercial HVAC, electrical, and plumbing subs
Civil and infrastructure contractors
Homebuilders and residential developers
Architecture and engineering (A&E) firms
Typical turnaround for indication of terms: 1 business day.
Defense
CMMC, DFARS, and CUI-compliant risk transfer
CMMC
2.0 compliance required by 2026
Common threats we underwrite against
▣ CUI exfiltration
▣ Nation-state APTs
▣ Supply-chain compromise
▣ Cleared-personnel targeting
Sub-sectors we place
DoD prime contractors
CMMC-regulated subcontractors
Defense software and systems integrators
Aerospace and satellite contractors
Federal IT and cleared staffing firms
Typical turnaround for indication of terms: 1 business day.
The Bloc system
One foundation.
Ten industry-specific builds.
The Bloc mark is built from stackable planes — each one a different angle on the same core structure. That’s how we place coverage: one underwriting discipline, tuned and re-tuned for every industry we serve.
Coverage
A policy you can actually read.
Structured in three clean blocs.
01
First-Party
Your direct losses when an incident hits your business.
✓
Incident response & forensics
✓
Business interruption
✓ Data restoration
✓ Cyber extortion / ransomware
✓ Funds transfer fraud
✓ Reputational harm
02
Third-Party
Your liability to clients, partners, and regulators.
✓
Network security liability
✓
Privacy liability (HIPAA, GDPR, state laws)
✓ Regulatory defense & fines
✓ PCI-DSS fines and assessments
✓ Media liability
✓ Breach notification costs
03
Specialty
Advanced coverages for complex risks and contracts.
✓
Technology E&O
✓
Social engineering fraud
✓ Contingent business interruption
✓ Systems failure
✓ Bricking & hardware replacement
✓ CMMC / regulatory-specific endorsements
Typical limits placed
$1M / $1M starter
$5M / $10M mid-market
$25M+ layered towers
Custom retentions
Common Questions
Cyber Liability Insurance, Explained
What does cyber insurance cover?
Cyber insurance covers the financial losses from a data breach or cyberattack. This includes breach response, legal fees, customer notification, ransomware, business interruption, and regulatory fines, depending on your policy.
Does my business really need cyber insurance?
Yes. Any business that stores customer data, processes payments, or relies on connected systems faces cyber risk. Small and mid-sized companies are frequent targets because they often have fewer defenses.
How much does cyber insurance cost?
Cost depends on your industry, revenue, data volume, and security practices. We market your risk to multiple carriers to find strong coverage at a competitive price. Request a quote for an exact figure.
What is the difference between first-party and third-party cyber coverage?
First-party coverage pays for your own losses, like data recovery and lost income. Third-party coverage pays for claims from others harmed by a breach on your systems.
How fast can I get a quote?
Most clients receive a quote in under 24 hours after we review the details of their business and exposure.
What should I do first after a cyberattack?
Contact us right away. We help you start breach response, connect you with forensic and legal support, and guide your claim so you contain the damage quickly.
Insights
Field notes from the placement desk.
What carriers are asking right now.
Start a quote
Tell us about your business.
We’ll come back with terms.
We’ll review your stack, your contracts, and your exposure — then place the program against the right markets. Most intakes get indicative terms back within one business day.
01
Quick intake
We only ask what the carriers actually need.
02
Benchmark
Side-by-side terms from 10+ specialty cyber carriers.
03
Bind
Plain-language policy review, e-signed and in force.
