Find out what an attacker could reach in your network, applications and cloud, with proof your board, your auditors and your engineers can each act on.
InfoSight is a Miami Lakes cybersecurity firm founded in 1998, serving organizations across Miami-Dade, Broward and Palm Beach counties with U.S.-based, certified testers.
Just Researching Costs?
Get a preliminary budget estimate without scheduling a consultation or speaking with a salesperson.
A Coral Gables clinic, a Doral freight forwarder and a Boca Raton lender with a New York license will each read this table differently.
| Rule | Who it reaches | What it asks for |
|---|---|---|
| Interagency Guidelines and NCUA Part 748, Appendix A | Banks, savings associations and federally insured credit unions | Regular, risk-based testing of key controls by independent parties or staff; no penetration test or annual interval is named. |
| PCI DSS Requirement 11.4 (v4.0.1 is the active version) | Businesses in PCI DSS scope that handle card data | Internal and external tests at least once every 12 months and after any significant infrastructure or application change, by a qualified, organizationally independent tester; exploitable findings corrected and retested; segmentation controls, where used, tested at least every 12 months and after changes to them (every six months for service providers). |
| FTC Safeguards Rule, 16 CFR 314.4(d)(2) | Non-bank financial institutions such as mortgage brokers, finance companies and check cashers | Absent effective continuous monitoring or other ongoing vulnerability-detection systems: annual penetration testing scoped by the risk assessment, plus vulnerability assessments at least every six months and after material changes. Firms with customer information on fewer than 5,000 consumers are excepted from this paragraph (16 CFR 314.6). |
| HIPAA Security Rule, 45 CFR 164.308(a)(8) | Covered entities and business associates | A periodic technical and nontechnical evaluation; penetration testing is not named. A January 2025 proposal would require one at least every 12 months, with vulnerability scans every six; as of October 2026 it is not final. |
| NYDFS, 23 NYCRR 500.5(a)(1) | New York-licensed banking, insurance and financial services firms, including Florida ones (size exemptions apply) | Penetration testing from inside and outside the information systems' boundaries by a qualified internal or external party at least annually, plus automated scans and manual reviews at a frequency set by the risk assessment (500.5(a)(2)). |
| Florida Statutes s. 501.171 | Businesses and government entities holding Floridians' personal information, with their third-party agents reporting to them | Reasonable measures to protect personal information; no test is named. Notice to affected Floridians within 30 days of determining the breach, and to the Department of Legal Affairs when 500 or more people in Florida are affected. |
| Florida Statutes s. 282.3185 | Counties and municipalities | Standards consistent with best practices, including the NIST Cybersecurity Framework; ransomware reported within 12 hours of discovery, severity level 3 to 5 incidents within 48. No penetration test required. |
In the table, only PCI DSS, the FTC rule and NYDFS name a penetration test. In our view a test is still one of the clearest ways to show Florida's "reasonable measures" hold up.
Need a broad inventory rather than exploitation? Start with a vulnerability assessment. Writing your own software? Secure code review catches flaws before they ship.
Book a zero-cost 15-minute scoping call and instantly receive a preliminary scan report to share with stakeholders and executives.
Prefer to talk it through now? Call 305.828.1003.
InfoSight, 14100 Palmetto Frontage Rd, Suite 310, Miami Lakes, FL 33016
What will it cost? Price follows scope, and our guide to what a penetration test costs explains the drivers.
It depends on scope. A single internet-facing perimeter is a much smaller job than an internal network with Active Directory, several web applications and a cloud tenant, and the scoping call is where that gets defined.
A clear scope (IP ranges, application addresses, cloud accounts), test accounts for authenticated testing, a named contact for the testing window and a list of anything off limits. Those details go into the rules of engagement before testing begins.
Anything that must not be touched is written into the rules of engagement as off limits, and windows can run off-peak. For OT networks, InfoSight tests against live process data without disrupting production.
The report is written for that reader: a leadership summary, technical detail and findings mapped to MITRE ATT&CK and NIST 800-53. PCI DSS also expects exploitable findings to be corrected and the test repeated to verify them, which InfoSight's on-demand re-testing is built for. Acceptance is your assessor's or examiner's call, so share the planned scope first.
It depends on the test. External testing comes in over the internet, as an outside attacker would. Social engineering and physical tests, such as tailgating and badge-cloning drills, happen at your sites. How internal testing is delivered is settled during scoping.
After you patch, click Re-Test in the Mitigator portal and InfoSight re-attacks those CVEs within 24 hours to validate the fix. The finding and its status stay in Mitigator, so the evidence is there at the next audit.
It starts with a zero-cost 15-minute scoping call. The systems in scope, the type of assessment and the testing window are agreed before testing begins. For a planning figure, the budgetary estimate form gives a preliminary number without a sales call.
A scan does not replace a test. NIST describes penetration testing as evaluators mimicking real-world attacks, often combining vulnerabilities to gain more access than any single one allows. The FTC Safeguards Rule lists the two as separate items.