Every safeguards obligation your firm carries, Reg S-P, your fiduciary duty, your insurance representations, the breach-notification clock, shares one silent prerequisite: knowing where customer information actually lives. Most firms cannot answer that question with a document. They answer it with a person, usually whoever has been in operations longest, and that person’s memory is the firm’s de facto data map.
The amended Reg S-P made this gap concrete. You cannot assess whether “sensitive customer information” was accessed within 30 days if you need the first three weeks to figure out which systems held it. And the rule’s expanded scope, customer information in your possession regardless of whose customer it is, means the map has to cover data you never chose to collect.
What a usable inventory looks like
Not a data-governance platform. A worksheet with a row per repository and five columns:
- Where: the system or location. Email, CRM, portfolio management, custodian portal, file server, the shared drive, DocuSign, the scanner’s hard drive, the off-site storage unit with the 2014 paper files.
- What: which categories of NPI: SSNs, account numbers, statements, government IDs, medical information from insurance work.
- Whose: your clients, prospects who never converted, employees, other firms’ customers received in transfers.
- Who can touch it: roles, not names, plus which vendors have access paths.
- How it leaves: the disposal story: retention period, deletion mechanism, and whether anyone has ever actually run it.
The first pass takes a focused afternoon, and the first pass is always wrong in the same two places: email and exports. Email is a shadow copy of nearly every other repository: statements, completed forms, scanned IDs sitting in sent-mail forever. And every system on the list leaks spreadsheet exports onto laptops and shared drives. Your inventory should name both honestly rather than pretend the diagram is clean.
What the map immediately buys you
- A real breach scope. When a laptop disappears or a mailbox is compromised, the inventory converts “we’re investigating” into “that repository held X for Y clients”: the difference between a controlled notification decision and a panicked one.
- A defensible disposal program. The Data Disposal Policy stops being aspirational the moment each repository has a named deletion mechanism. Old prospect data with no retention, legal, or business purpose is pure liability; the map is how you find it.
- Smaller vendor surface. Mapping access paths usually surfaces a vendor or two with standing access nobody remembers granting. Revoking it is free risk reduction.
- A faster exam. “Provide an inventory of systems containing customer information” appears, in some phrasing, in nearly every cybersecurity document request. Producing it in minutes sets the tone for everything after.
Keep it alive with one question
The inventory dies if it’s an annual project. It lives if one question gets added to your new-vendor checklist and your annual review: did any repository of customer information get added, moved, or retired this year? Five minutes, four quarters, and the map stays truer than most firms’ network diagrams.
BrainTrust members: the NPI Data Inventory Worksheet in the library is the five-column structure above, pre-seeded with the repositories that appear at almost every advisory firm. Fill it in once; maintain it by exception.