When an examiner, an auditor or a major customer asks how your defenses were tested, answer with a real attack, run under rules you approve.
For organizations from Dallas and Plano to Fort Worth and Arlington: U.S.-cleared, certified testers run every assessment.
Just Researching Costs?
Get a preliminary budget estimate without scheduling a consultation or speaking with a salesperson.
Only some of these rules name a penetration test; the others set broader security duties and leave the method to you.
Forty-two FDIC-insured institutions are headquartered in the four counties, 22 in Dallas County and 11 in Tarrant; NCUA's June 2026 records list 50 federally insured credit unions with mailing addresses in the four counties; finance and insurance firms counted 246,167 private-sector jobs in March 2026. The Federal Reserve Bank of Dallas serves the Eleventh District from Dallas. More on financial institutions.
The rules
Banks and federally insured credit unions: regular, risk-based testing of key controls by independent parties or by staff independent of those who run the security program; the Interagency Guidelines and NCUA Part 748, Appendix A name no penetration test or annual interval. Non-bank lenders under the FTC Safeguards Rule: an annual penetration test scoped by the risk assessment, unless effective continuous monitoring or other ongoing vulnerability-detection systems are in place, plus vulnerability assessments every six months and after material changes; firms with customer information on fewer than 5,000 consumers are excepted from the testing paragraph. New York licensees under its banking, insurance or financial services laws: NYDFS 500.5(a)(1), an annual test from inside and outside the system boundaries, subject to size exemptions.
Private health care and social assistance employers counted 415,074 jobs across the four counties in March 2026, 100,254 of them in hospitals. More on health care security and HIPAA risk assessments.
The rules
The HIPAA Security Rule requires covered entities and business associates to evaluate their security periodically. It does not name penetration testing. A January 2025 federal proposal would require a penetration test at least every 12 months and vulnerability scans every six months; as of October 2026 it has not been finalized, and the federal regulatory agenda lists it as a long-term action.
Private telecommunications employers counted 30,377 jobs across the four counties in March 2026, computer systems design firms 115,779 and corporate head offices, regional managing offices and holding companies 68,206.
The rules
Card data brings PCI DSS Requirement 11.4: internal and external tests at least once every 12 months and after any significant infrastructure or application change, by a qualified, organizationally independent tester, with exploitable findings corrected and retested; segmentation, where used, is tested every 12 months and after changes (every six months for service providers). PCI DSS is a payment-industry standard enforced through card brands and acquirers, not a law. The Texas Data Privacy and Security Act requires covered companies to keep reasonable administrative, technical and physical data security practices; the Texas Attorney General enforces it.
The City of Dallas's own report on its May 2023 ransomware attack traces entry through a service account and movement across the network with legitimate remote management tools; the city told the Texas Attorney General that 26,212 Texas residents' personal information was potentially exposed. An internal penetration test asks the same question: how far one account can reach. See our public sector work.
The rules
State agencies: since September 1, 2025, Texas law directs the Texas Cyber Command to require each agency to complete an information security assessment and a penetration test at least once every two years, performed by the Command or a vendor it selects (Gov't Code 2063.409; universities excepted), and agency websites and apps that process sensitive or confidential information need a vulnerability and penetration test, with the findings addressed (2063.405). Cities and counties: annual certified cybersecurity training for officials and employees with access to their systems, and a 48-hour report to the Command of incidents involving sensitive or regulated data, with no penetration test named.
Book a zero-cost 15-minute scoping call and instantly receive a preliminary scan report to share with stakeholders and executives.
Rather talk it through first? Call 305.828.1003.
InfoSight is based in Miami Lakes, Florida, and serves clients nationwide.
External, application, API and cloud testing can be performed remotely wherever you operate; how the internal test reaches your network is agreed during scoping.
Physical and in-person social engineering tests take place at your sites, from tailgating and badge cloning to camera blind spots.
A scope you approve up front, every action documented, in 24 × 7, 8 × 5 or off-peak windows.
Findings move into Mitigator, InfoSight's risk intelligence platform, where you track remediation status, MTTR and SLA performance long after the engagement ends.
Budgeting first? Use the estimate form at the top of this page, or see the ranges security vendors publish on our penetration testing cost page.
For the tests that need it: physical and in-person social engineering tests take place at your sites, while external, application, API and cloud testing can be performed remotely. How internal testing is delivered is agreed during scoping.
A zero-cost 15-minute scoping call, which comes with a preliminary scan report, then an agreed scope and rules of engagement: test accounts, a named contact and anything off limits. Testing is scheduled once those are set.
It depends on which rule applies. PCI DSS Requirement 11.4 calls for internal and external tests at least every 12 months and after significant changes. The FTC Safeguards Rule sets annual testing for the institutions it covers unless they run effective continuous monitoring or other ongoing vulnerability detection, and New York's DFS regulation sets an annual test for covered entities, subject to size exemptions. HIPAA requires a periodic evaluation but does not name penetration testing. Outside those rules, your risk assessment and your rate of change set the cadence, and the scoping call turns it into a schedule.
Yes, if you are in PCI DSS scope: Requirement 11.4 calls for internal and external tests at least once every 12 months and after any significant change. InfoSight maps findings to PCI DSS; acceptance is your assessor's or acquirer's call.
Texas requires a business that suffers a breach of sensitive personal information to notify affected individuals without unreasonable delay and no later than the 60th day after it determines the breach occurred, and to notify the Texas Attorney General as soon as practicable and no later than the 30th day after it determines the breach occurred, when 250 or more Texans are affected. Texas law also requires businesses other than financial institutions under the federal Gramm-Leach-Bliley Act to keep reasonable procedures to protect that information; neither duty names a penetration test.
A high-level risk narrative for leadership and the board, and step-by-step exploit detail for the engineers who fix it, with each finding mapped to MITRE ATT&CK and NIST 800-53 controls. After you patch, click Re-Test in the Mitigator portal and the testers re-attack those CVEs within 24 hours to validate the fix.