Skip to content

GLBA penetration testing

GLBA penetration testing is the annual test many financial firms need to satisfy the Safeguards Rule. This page explains the rule for mortgage brokers, tax preparers, lenders and dealers, and shows how one yearly test plus a maintenance plan covers it.

What is GLBA penetration testing?

GLBA penetration testing is a real security test run to satisfy the Gramm-Leach-Bliley Act. GLBA is the parent law; its security requirements for non-bank financial institutions are carried out by the FTC Safeguards Rule at 16 CFR Part 314. That rule asks covered firms to test their defenses, and a penetration test is how most of them do it.

In practice this means a tester tries to break into your systems the way a real attacker would, then reports what they got to and how to close it. Grapefruit runs that test at a fixed price, with authenticated coverage of your web app, your APIs and any AI features, and the report in about 10 days.

How does GLBA connect to the Safeguards Rule?

GLBA sets the goal; the Safeguards Rule sets the mechanics. The act directs financial institutions to protect customer information, and it tells the FTC to write the rules that make that concrete. The result is the Safeguards Rule, 16 CFR Part 314, which spells out the written information security program a covered firm must maintain, including the testing piece.

So when people say GLBA penetration testing, they mean the testing the Safeguards Rule requires under GLBA's authority. The definitions that decide who is covered and what counts as a test live in 16 CFR 314.2. The testing duty itself lives in 16 CFR 314.4(d).

What does 314.4(d) require for testing?

The rule gives you a choice. Under 16 CFR 314.4(d), a covered firm must either continuously monitor its systems, or do both annual penetration testing and vulnerability assessments at least every six months. Most firms cannot run full continuous monitoring, so they take the second path: one annual test plus recurring scans.

A penetration test and a vulnerability assessment are not the same thing, and the rule asks for both on that path. The annual test tries to defeat your controls and prove real impact. The six-month assessments are recurring checks for weaknesses between tests. Both must also respond to material changes, so a new system or feature triggers fresh testing.

  • Path one: continuous monitoring of systems for changes and intrusions.
  • Path two: an annual penetration test, plus vulnerability assessments at least every six months.
  • Either path must respond to material changes to your systems or operations.
  • This testing requirement has been enforceable since June 9, 2023.

Who must comply with GLBA's Safeguards Rule?

The rule reaches a wide range of non-bank businesses. Financial institution is defined broadly under 16 CFR 314.2, and the rule and FTC guidance name many everyday businesses that handle customer financial information. If you lend, finance, broker, prepare taxes, collect debts or move money, you are likely covered.

If one of the businesses below describes you, and you maintain customer information on 5,000 or more consumers, the testing requirement applies to you.

  • Mortgage brokers and mortgage lenders.
  • Tax preparers.
  • Auto dealers that finance or lease vehicles.
  • Payday, installment and other non-bank lenders, and finance companies.
  • Collection agencies.
  • Check cashers, money transmitters and wire-transfer services.
  • Investment advisers and credit counselors.

Who is exempt under the 5,000-consumer rule?

Small firms get a partial exemption. Under 16 CFR 314.6, a business that maintains customer information on fewer than 5,000 consumers is exempt from the testing requirement, along with a few other provisions. Cross 5,000 consumers and the annual-test-plus-scans requirement applies in full.

The count is where firms slip. Consumer information adds up across years of files, not just this year's active clients. A tax preparer who has filed for a few thousand clients over several seasons, or a broker with years of closed loans on record, is probably over the line. When the number is close, treating testing as required is the safe call.

How does Grapefruit meet GLBA's testing duties?

Grapefruit maps onto both halves of the periodic path. The annual penetration test is one Grapefruit full test a year. The six-month scanning half is a Grapefruit maintenance plan that re-tests your verified domains every week or month, well inside the six-month line and dated for your file. One full test a year plus a maintenance plan covers both duties.

The table lines up each duty with what it means and how the service meets it.

  • Web app, APIs and AI features are tested together in one engagement.
  • Findings are ranked critical, high, medium or low, each with the request and response that proves it.
  • Replay a finding before the fix and after it to confirm the issue is closed.
  • Every run is dated and downloadable, building the trail an examiner reviews.
GLBA Safeguards Rule dutyWhat it meansHow Grapefruit meets it
Annual penetration test, 314.4(d)A real test, inside or outside, that tries to defeat your controls once a yearOne full penetration test at a fixed quote, report in about 10 days, replayable evidence per finding
Vulnerability assessments every six monthsRecurring checks for weaknesses between the annual testsA maintenance plan re-testing verified domains weekly or monthly, well inside the six-month line
Testing after material changesFresh testing when you add or change a systemWeekly or monthly runs catch new endpoints and features on the next scheduled test
Evidence for an examinerProof the testing happened and findings were acted onDated runs in the portal showing new and fixed findings, each with captured request and response

How do you start GLBA testing with Grapefruit?

Add your hostname, publish one DNS TXT record and sign the testing authorization online. It takes a few minutes. Testing starts right after, using test accounts you supply for authenticated coverage, and the report lands in about 10 days at a fixed price. No demo call, no scheduling.

Pick a full penetration test at a fixed quote for the annual duty, and a maintenance plan for the six-month scanning duty. Not sure you are covered? Run the compliance check first, or see pricing to compare. This is a summary of public rules, not legal advice.

Questions

Does GLBA require a penetration test?
GLBA itself directs firms to protect customer information; the detail lives in the FTC Safeguards Rule it authorizes. Under 16 CFR 314.4(d), a covered firm either continuously monitors its systems or runs an annual penetration test plus vulnerability assessments at least every six months. Most non-bank firms take the second path, so an annual test is the practical way to comply.
What is the difference between GLBA and the Safeguards Rule?
GLBA is the parent law. It tells financial institutions to safeguard customer information and directs the FTC to write the rules. The Safeguards Rule, 16 CFR Part 314, is that rulebook, and it sets out the written security program and the testing duties. GLBA penetration testing means the testing the Safeguards Rule requires under GLBA.
I serve fewer than 5,000 customers. Do I still need to test?
Under 16 CFR 314.6, a firm that maintains customer information on fewer than 5,000 consumers is exempt from the testing requirement. The count adds up across years of files, not just active clients, so many firms that feel small are over the line. When you are close to 5,000, treating testing as required is the safe read.
My business is not a bank. Does GLBA apply to me?
Likely yes. The Safeguards Rule defines financial institution broadly under 16 CFR 314.2, and the rule and FTC guidance name mortgage brokers, tax preparers, auto dealers that finance, collection agencies, non-bank lenders, money transmitters and more. Handling customer financial information is what pulls you in, not the word bank on your sign.
How often do I need GLBA penetration testing?
On the periodic path, once a year, with vulnerability assessments at least every six months and after any material change to your systems. A Grapefruit full test covers the annual duty, and a maintenance plan re-tests your verified domains weekly or monthly, which sits well inside the six-month line and dates each run for your file.
How do I prove to an examiner that I tested?
Keep dated evidence. Each Grapefruit test and re-test is dated in your portal, with every finding ranked by severity and backed by a captured request and response. When a finding is fixed, a later run shows it gone. That dated record of testing and remediation is what an examiner looks for under the Safeguards Rule.

Standards and sources