FTC Safeguards Rule

A written program, a named person in charge and a yearly report, built from what you already do.

Already have an IT provider? Here's how we work together.

A tax and accounting firm, autumn

The written program nobody has written

The challenge. A firm of eight partners and staff handles clients’ tax returns, bank details and Social Security numbers. It has good habits: strong passwords, locked cabinets, an IT provider who patches. A client’s lender asks for the firm’s written information security program, and the firm has none.

The insight. The FTC Safeguards Rule asks for a written information security program based on a risk assessment, a qualified individual in charge, access controls, encryption, multi-factor authentication, staff training, service provider oversight, an incident response plan and a written report to the board or senior management at least once a year. The firm already does much of this; what is missing is the document and the record.

The decision. The partners named one of themselves as the person in charge and decided to write the program before the next busy season rather than during it.

The action. We ran a risk assessment with the partners and the IT provider, wrote the program from what the firm already did, and listed the gaps: multi-factor sign-in on the tax software, an inventory of client data, and an incident plan. The IT provider closed the technical gaps, and we checked the results. We drafted the first yearly report for the partners to sign.

The result. The firm answered the lender with a document and a record, and its insurer and clients can see the same. The program now has a yearly review date in the calendar.

What Security Medic does

Risk assessment

Where client data lives and moves, what could go wrong and how the controls hold up.

A written information security program

Built from what the firm does, covering each element the rule lists, with an owner for each.

The qualified individual’s support

Fractional leadership for the person named in charge, including the yearly report to leadership.

Service provider oversight

The IT provider, tax software and cloud vendors reviewed and recorded.

Where this sits in the cycle

Every client goes through the same six steps, from a town office to a family at home. The Security Medic method

  1. 1. Govern
  2. 2. Design
  3. 3. Assess
  4. 4. Review
  5. 5. Conform
  6. 6. Improve
  • Govern. A qualified individual named, a program approved and a yearly report to leadership.
  • Design. Controls designed around how client data moves through the firm.
  • Assess. The written risk assessment the rule requires.
  • Review. Gaps ranked and reported to the partners.
  • Conform. The IT provider and staff close the gaps; we check them.
  • Improve. Yearly review and report, and a check whenever systems or vendors change.

The standards we draw on

The FTC Safeguards Rule (16 CFR Part 314), which covers tax preparers, accountants, mortgage brokers, auto dealers and other financial institutions under the Gramm-Leach-Bliley Act, with the NIST Cybersecurity Framework 2.0 as the common structure. Applicability and notice duties (including notice to the FTC of certain security events) are confirmed for each client.

Policy and SOP writing →Third-party risk →Insurance readiness →

Getting ahead of it

Put the yearly report on the calendar a quarter before busy season, and the next year’s review will have time to matter.

Book a free 30-minute call about a written program

Tell us what you handle and what you already have in place. We will talk through what the rule asks and a sensible order of work.

Book a free 30-minute call