Insurance
Cybersecurity for insurance companies
An insurer holds years of personal, medical and financial detail about the people it covers, and shares access with agents, brokers and claims partners. We help insurers see what happens to that data across policy, claims and the portals around them, and keep the evidence their regulators ask for.
Overview
Insurance runs on information that people would rather keep private. To price a policy and pay a claim, an insurer collects identity documents, health records, property details and bank accounts, and keeps them for years. That information moves through policy administration systems, claims platforms, portals for agents and policyholders, and the partners who adjust, repair and reinsure. Every one of those places is a way in.
How attackers approach an insurer
The quickest route is an account someone already trusts. An agent's portal login, a claims handler's mailbox or a policyholder's online account can be used to read records, file a claim or send a payment somewhere new, and the activity looks like normal business. Other attackers go after the data itself, copying claim files and medical records and then demanding payment not to publish them.
Older systems make this harder to catch. Policy administration platforms that have run for decades often record little about who looked at what, and the newer claims and portal software beside them keeps its own separate logs. An agent login from an unusual place, a change to a payee's bank account and a large claim approved the same afternoon sit in three different systems, and none of them raises a flag alone.
Policy, claims and portals in one view
That is the problem we solved for a large insurer in the United States. We implemented a SIEM and brought into it the policy administration and claims systems, the portals used by agents, brokers and policyholders with their web and API servers, employee and administrator sign-ins with the directory and privileged accounts, and the data-centre and office networks, firewalls, cloud accounts and laptops. Alert rules follow the routes attacks take into an insurer, and they were tested and handed to the insurer's team with runbooks. Its logs are now in one place with alerts the team acts on, threats it could not see before are detected, and the logging evidence is ready for regulators and auditors. The work is our Threat Detection & SIEM Implementation service.
Insurance rules expect more than detection. Security Governance writes the security program the regulators ask for, and Threat Analysis & Risk Management provides the risk assessment it is based on. Red Teaming & Penetration Testing tests portals and claims workflows the way a fraudster would. Cybersecurity Training prepares the claims and underwriting staff who receive fake payment requests, and Compliance & Certification prepares you for ISO/IEC 27001 or a SOC 2 report when partners ask for one.
The rules insurers answer to
Insurers are regulated state by state in the United States. Many states have adopted the NAIC's Insurance Data Security Model Law, which asks for a written security program based on a risk assessment, audit trails, oversight of service providers and prompt notice to the commissioner. Insurers licensed in New York also follow Part 500, with its audit trail, monitoring and training requirements. Under the GLBA, each insurer's home state sets and enforces the safeguards for customer information. In Mexico, the CNSF's single circular requires internal controls that keep information systems secure and leave evidence the regulator can inspect.
We don't audit or certify against these rules. The standards we work with directly are ISO/IEC 27001, SOC 2 and NIST, and what we build is the program, the logging and the records that let you show an examiner how the rules are met.
Evidence that lasts beyond the project
An examination can come years after a system was set up, so the record matters as much as the controls. Every log source is documented with what it collects and how long it is kept, every alert rule has a runbook, and the decisions behind them are written down. Your team keeps all of it when we hand over.
Threat landscape
What attackers go after
Policyholder data held for years
Applications, medical reports, claim files and bank details stay on file for as long as a policy runs and often long after. That concentration makes an insurer a prime target for theft and for ransomware groups that threaten to publish what they take.
Agent and broker accounts
Independent agents and brokers sign in to quote, bind and service policies from their own offices and devices. A stolen agent login reaches policyholder records and quotes the insurer cannot easily tell apart from the agent's real work.
Fraud through the claims process
Attackers who take over a policyholder or staff account can file claims, change the bank account a payment goes to or approve what should be checked. Email that imitates an adjuster, a repair shop or a claimant is a common start.
Ageing policy administration systems
Many insurers still run policies on systems written decades ago, alongside newer claims and portal software. Older platforms are hard to patch and often record little about who did what, which leaves gaps exactly where the oldest data lives.
Partners that share the data
Third-party administrators, adjusters, medical reviewers, repair networks and reinsurers all receive policyholder data or connect to the insurer's systems. Each connection extends the insurer's exposure to a company whose security it reviews but does not run.
Compliance
The regulatory landscape, mapped
| Rule | Where | What it demands | How we help |
|---|---|---|---|
| NAIC Insurance Data Security Model Law | United States | In the states that have adopted it, insurers and other licensees must keep a written information security program based on a risk assessment, with audit trails that detect cybersecurity events, monitoring of systems, staff training, oversight of service providers and prompt notice of an event to the insurance commissioner. | Our governance and risk work builds the written program and its risk assessment, and the SIEM supplies the audit trails and monitoring the program describes. |
| NYDFS cybersecurity regulation (23 NYCRR Part 500) | United States | Insurers licensed under New York's Insurance Law are covered entities. They must keep audit trails designed to detect cybersecurity events, monitor the activity of authorised users, train all staff at least once a year and notify the Department of an incident, and larger companies must centralise logging and security event alerting. | Centralised logging with alerting on policy, claims and access is the core of a SIEM project, and the runbooks start the internal steps that lead to a notice. |
| Gramm-Leach-Bliley Act (GLBA) | United States | The GLBA requires financial institutions, including insurers, to protect the security and confidentiality of customers' nonpublic personal information. For insurance companies the safeguards are set and enforced by the state insurance authority of the state where the company is domiciled. | The access controls, logging and testing we put in place give your state examiners concrete safeguards to review, documented in one place. |
| CNSF internal control rules (CUSF, disposición 3.3.3) | Mexico | Mexico's single circular for insurers and sureties requires an internal control system that keeps information systems operating under the institution's security policies and preserves the security of the information they generate, receive, transmit, process or store, with evidence available to the CNSF. | Logs and alerts from policy, claims and access systems show that the security policies are applied in practice and leave a record the CNSF can inspect. |
Services
The services for this sector
Threat Detection & SIEM Implementation
Policy, claims, portals and staff access each keep their own records. A SIEM brings them together, so a hijacked agent account that then changes a claim payment shows up as one event rather than two quiet ones.
Security Governance
The NAIC model law and Part 500 both start from a written security program with named owners, policies and board reporting. We write that program around the controls you already run.
Threat Analysis & Risk Management
Insurance rules ask for a risk assessment that the program is based on. We assess the threats to policyholder data, agents and claims, and rank what to fix first.
Red Teaming & Penetration Testing
Testing the agent and policyholder portals, claims workflows and internal network as an attacker would shows where a payment can be redirected or records reached before a fraudster finds it.
Compliance & Certification
Readiness for ISO/IEC 27001 or a SOC 2 report gives reinsurers, partners and large corporate clients an independent view of your controls, built on the same logging and governance.
Cybersecurity Training
Claims handlers, underwriters and agents receive the fake payment requests and claimant emails first. Training built around those messages helps them spot one before money moves.
Example project
Threat detection across an insurer's policy, claims and portal systems
We implemented a SIEM for the insurer and brought four groups of logs into one place. The policy administration and claims systems came first. Next were the portals used by agents, brokers and policyholders, with the web and API servers behind them. Identity followed, with employee and administrator sign-ins, the directory and privileged accounts. Last came the data-centre and office networks, firewalls, cloud accounts and staff laptops. We wrote alert rules for the ways attacks reach an insurer through each group, tested them and handed the platform to the insurer's team with runbooks.
- Client
- A large insurer in the United States
- Result
- Logs from policy and claims systems are in one place with alerts the team acts on, threats that were not visible before are detected, and logging evidence is ready for regulators and auditors.
FAQ
Frequently asked questions
Will the SIEM give us the logging evidence our state examiners and NYDFS ask for?
It gives you the records and shows how they are produced. Each source is documented with what it logs and how long the data is kept, and every alert has a runbook and a trail of what was done. That is the material examiners review. Whether it meets a specific rule is their judgement, not ours.
Will this help with the questions our own cyber insurer or reinsurer asks?
It helps you answer them. Cyber underwriters and reinsurers ask whether you log security events, alert on them, protect privileged accounts and test your defences. After the project you can describe each of those with evidence. We make no claim about premiums or terms; those are your underwriter's decision.
Can you collect logs from our older policy administration and claims systems?
Usually, yes. Where an older system cannot send logs itself, we read them from its database, the server it runs on or the files it writes, and check that each source delivers complete events before relying on it. Where a system records almost nothing, we say so and watch the sign-ins and network traffic around it.
Do you work with insurers in Mexico?
Yes. We work in English and in Spanish, from offices in Fort Lauderdale and Zapopan, and Spanish-speaking teams can write to contacto@guilda.mx. For an insurer supervised by the CNSF, the internal control rules on information security and the evidence they require shape what we log and how the runbooks are written.
Industries
Explore your sector
Next step
Tell us what your regulators ask to see
Name your policy, claims and portal systems, the states or countries you answer to and any examination coming up. We reply within two business days.