Show us your information inventory
In New York, 23 NYCRR 500.13(a) has insurers keep a complete, documented inventory of information systems, tracking, as applicable, each asset’s owner, location and classification or sensitivity.
Insurance. Claims. Policy administration.
Claims tables and broker exports can carry policyholder data well beyond the policy system. IRIS finds it in the stores you connect and shows who can reach it.
Four paid engagements and three proofs of concept.
In New York, 23 NYCRR 500.13(a) has insurers keep a complete, documented inventory of information systems, tracking, as applicable, each asset’s owner, location and classification or sensitivity.
Section 4.D(2) of the NAIC Insurance Data Security Model Law lists measures a licensee adopts as its risk assessment warrants, among them identifying and managing the data the business runs on.
A health insurer is a health plan under HIPAA, 45 CFR 160.103, so medical details in its claims files are protected health information.
Records from one scan of an insurer’s policy, claims and finance stores, with one candidate rejected and one partner system out of reach.
| Source | Location | Detected type | Why | Sensitivity | Decision |
|---|---|---|---|---|---|
| Policy administration database | policy.holder.date_of_birth | Date of birth | Underwriting data on every policyholder | Confidential | Keep; limit reads to underwriting and policy servicing |
| Claims database | claims.claimant_health.medical_conditions | Health information (medical record) | A health table joined to bodily-injury claims | Restricted | Keep for the claim; restrict to the claims team handling it |
| Payout database | finance.payouts.bank_account | Bank account number | Claim payout details, readable by the whole finance group | Restricted | Narrow reads to the payments role; record the reviewer |
| Broker exports (SharePoint) | Brokers/Renewals/renewal_list_q4.xlsx | US Social Security number | A renewal list sent to a broker, with identifiers it didn’t need | Restricted | Remove the identifiers; re-send a minimal list |
| Claims database | claims.claim.reference | US SSN (candidate) | Nine-digit claim references in the SSN format | None | Rejected by the reviewer: claim numbers, not SSNs |
| Third-party administrator | The administrator’s claims platform | Not scanned | Run by the administrator under contract; no read access | Unknown | Excluded: covered by the contract’s security terms, and listed as a gap |
The NAIC model law is adopted state by state, so check your state’s version of Section 4.D(2)(b) and the notice deadline it sets in Section 6. New York’s Part 500 (DFS’s unofficial copy; the official text is in the NYCRR) applies to DFS-licensed insurers, and compliance with its inventory rule in 500.13(a) has been required since November 1, 2025.
In the EU, health details in a claim are special category data under GDPR Article 9, and UK GDPR keeps the article. This page doesn’t map GLBA’s privacy rules or state insurance privacy laws. In India, IRDAI’s Information and Cyber Security Guidelines, 2026 cover data classification in Policy 2.1 and the asset inventory in clause 3.2.2.2.
Our position: an examiner who asks for the inventory will ask how you know it is complete, so keep the scan’s coverage record beside it.
“Different claims jobs need different data,” as Dipal Panchal put it in a published post. A fraud analyst and a payments clerk shouldn’t see the same claim file.
Shows the roles that can read each claims table, from table and view grants, and flags admin rights on the tables with health details.
Renewal and claims lists leave for brokers and administrators. Check each outgoing file for identifiers the partner has no use for before it is sent.
Classifies the files in the connected folders exports leave from, so an identifier in a broker list is found before the next send.
Flags columns named for medical conditions, medications or allergies as health information. A diagnosis written as prose in a notes field isn’t detected, so review notes by hand.
Maps people, roles and service accounts to the claims and payout tables they can read, so each claims job’s access can be checked against its need.
Checks sampled values for encryption, masking or hashing, once the check is activated on your install, and flags policyholder identifiers held in plain form.
Each scan records the stores it covered and those it couldn’t read, with reasons, so the inventory comes with its own completeness record.
Capabilities vary by edition.
The insurer approves what is shared with partners; IRIS doesn’t control onward transfers, and it can’t see a third-party administrator’s platform you haven’t connected.
It doesn’t decide which claims job needs which field, and it doesn’t change access. Your claims and IT owners make both calls, and a re-scan records the result. Because each scan is dated and IRIS reads a sample of each table, and small tables in full, give the examiner the scan dates with the inventory.
How each law treats personal and health data.
IRIS doesn’t score NAIC model law, Part 500 or IRDAI guidelines. UK GDPR and UAE PDPL: IRIS maps evidence to their controls. A scored view for these in insurance isn’t in v1; ask us if you need one.
Scan the claims database and the folders broker exports leave from in one run, since health tables and outgoing lists carry health details beyond the claims team. The how-it-works page follows that run to its findings.
Part of it. IRIS lists the data stores that hold sensitive data and their coverage; owners, hardware and the written policies and procedures stay with your team.
Yes, HIPAA is one of the six frameworks IRIS scores. The evidence covers the systems you connect, and your auditor judges whether each control is met.
No, unless the broker’s system is connected. Record those copies as gaps, under the contract that governs them.
Name the claims database your last examiner sampled. We’ll show what IRIS finds in it and who can read it.