Do title companies need a penetration test?
Yes, in practice. Real-estate settlement services fall under the FTC Safeguards Rule as financial institutions, and one way to meet its security-testing requirement is annual penetration testing plus vulnerability assessments every six months. Title agencies also sit at the center of real-estate wire fraud, so the stakes are higher than the rule alone.
You hold the pieces a fraudster needs in one place: the buyer's and seller's identities, the lender payoff letter, the closing disclosure and, above all, the wire instructions that tell where hundreds of thousands of dollars should go. Protecting those systems is both a legal expectation and basic survival.
Grapefruit runs the test the rule points to: a real attack on your systems, every finding proven, at a fixed price, with the report in about 10 days.
What does the FTC Safeguards Rule require?
The Safeguards Rule, at 16 CFR 314.4(d), gives you a choice. You can continuously monitor your systems, or do both annual penetration testing and vulnerability assessments at least every six months, and again after any material change. For a settlement agency the testing path produces a dated record your underwriters and lenders can rely on.
At 16 CFR 314.2 the rule defines a penetration test as a method where testers try to defeat your security from outside or inside your systems. Grapefruit does that with authenticated testing, using test accounts you supply, so the attack mirrors what a logged-in closer, buyer or agent could reach.
- Annual penetration testing: one full Grapefruit test a year covers this half.
- Vulnerability assessments every six months: a Grapefruit maintenance plan re-tests weekly or monthly, well inside the line.
- After material changes: a plan re-tests after you connect a new lender system or closing-portal feature.
- In force since June 9, 2023, so the expectation is current.
Are you a covered financial institution?
Very likely. The rule and FTC guidance describe financial institutions broadly, reaching the services that support real-estate lending and settlement. If you hold escrow, issue closing documents or transmit funds, you process the nonpublic personal information the Safeguards Rule protects. The definition sits at 16 CFR 314.2.
There is a narrow exemption. Under 16 CFR 314.6, a firm that maintains customer information on fewer than 5,000 consumers is exempt from the testing requirement. Count both sides of every deal, plus agents and prior closings, before relying on it, because closing volume adds up quickly.
No certification is required to run the test. The rule asks for a competent tester, not a licensed one, because there is no federal penetration-testing license.
What does a title company breach look like?
It is almost always about the wire. An attacker who gets into the closing portal, or into an inbox or document store tied to it, swaps the account number on the wire instructions the buyer receives. The buyer sends the down payment or the full purchase price to the fraudster, confident it is going to the title company. By the time anyone notices, the money has moved on.
The access that enables it often looks mundane: a closing file that loads by a guessable ID, a payoff letter stored where an attacker can reach it, or a portal login that was never scoped to one transaction. Grapefruit hunts those paths and proves which ones actually open.
- Wire instructions that can be altered, viewed or re-sent by someone who should not reach them.
- Closing files that load across transactions through a changeable ID.
- Payoff letters and IDs exposed through an unprotected API endpoint.
- Closing portals or document stores reachable without the right login.
What does Grapefruit test for a settlement agency?
Everything a closing touches, in one test. The closing portal, the APIs that move documents and fund data, and any AI assistant you use for intake or status updates are attacked together, because a real attack chains across them. Findings are ranked critical, high, medium or low in an online portal.
Every finding arrives with the exact request and response that proves it. Your engineer pastes the request, runs it, watches a wire record or closing file expose, then fixes it and runs the same request to watch the attack fail. That before and after is evidence an underwriter or insurer can trust.
- Authenticated testing with test accounts you supply, across closer, buyer and agent roles.
- Access-control and business-logic testing focused on funds and wire data.
- API testing mapped to the OWASP API Security Top 10 2023.
- A downloadable report with the tested hostnames, the run date and proof for every finding.
| Closing-day data | Attack that reaches it | What Grapefruit does |
|---|---|---|
| Wire instructions | Tampering to redirect funds | Tests who can view, alter or resend them |
| Closing files | Broken object level authorization by ID | Attempts to load files across transactions |
| Payoff letters and IDs | Unprotected API endpoint | Probes the API for sensitive records |
| Escrow and status data | Portal login not scoped to one deal | Tests role and transaction boundaries |
How does one test a year plus a plan cover the rule?
The Safeguards Rule's two halves match Grapefruit's two offers. One full penetration test a year satisfies the annual testing requirement. A Grapefruit maintenance plan re-tests your verified domains every week or month, which sits inside the six-month vulnerability-assessment line and dates each run for your file.
So one full test a year plus a maintenance plan covers both halves of the rule, and gives you a standing watch on the systems that move closing funds. See pricing to configure a full test, or to start a plan.
How do you start?
Add your hostname, publish one DNS TXT record and sign the testing authorization online. It takes a few minutes. Testing without authorization is a federal crime under the Computer Fraud and Abuse Act, 18 U.S.C. 1030, which is why Grapefruit takes a signed authorization and a defined scope before any test.
Results land in your portal within hours of kickoff. Choose a full penetration test at a fixed quote, or a maintenance plan for weekly or monthly re-tests. This is a summary of public rules, not legal advice.
Questions
- Is penetration testing required for title companies?
- Real-estate settlement services fall under the FTC Safeguards Rule, which at 16 CFR 314.4(d) lets you meet its testing requirement with annual penetration testing plus vulnerability assessments every six months. Grapefruit runs that test at a fixed price with the report in about 10 days, and a plan keeps the six-month checks dated.
- How does a pentest help with wire fraud?
- Wire fraud usually begins with access an attacker should not have: a closing file that loads by a changeable ID, a reachable document store, or a portal login not scoped to one deal. Grapefruit finds and proves those paths before a fraudster can use them to alter the wire instructions a buyer receives.
- Is my small title agency exempt?
- Possibly. Under 16 CFR 314.6, a firm maintaining customer information on fewer than 5,000 consumers is exempt from the testing requirement. Count buyers, sellers, agents and prior closings before relying on it, because both sides of every deal add to the total and most active agencies pass 5,000 quickly.
- What closing data does Grapefruit protect?
- Wire instructions, payoff letters, IDs, escrow details and full closing files. Those are the records a fraudster needs and the data the Safeguards Rule covers. Grapefruit tests whether any of them can be viewed, altered or reached across transactions, through your portal, your APIs or an AI assistant.
- Do I need a certified tester?
- No. The Safeguards Rule asks for a competent tester, not a certified or licensed one, and there is no federal penetration-testing license. What matters to an examiner, an underwriter or an insurer is a real test with evidence, which a Grapefruit report delivers with the request and response behind every finding.
- Can you test our closing portal without touching real deals?
- Yes. Testing uses the hostnames and test accounts you supply, so we work against your systems with controlled accounts rather than live closings. You set the scope and the window, and a maintenance plan re-tests on a schedule so coverage continues as you add features or lender connections.