Cybersecurity for Financial Services: GLBA, FTC Safeguards & SOC 2 Guide | CyberStackHub
Financial services SMBs — independent RIAs, mortgage brokers, insurance agents, credit unions, fintech startups, and accounting firms — face overlapping federal and state cybersecurity regulations: GLBA, the FTC Safeguards Rule, NY DFS 23 NYCRR 500, SOC 2, and PCI DSS. Criminals know this sector holds the highest-value data (SSNs, account numbers, financial records) and that smaller organizations often lack the controls that big banks have. This guide covers which regulations apply to your business type, what controls they require, and how to close the gaps before regulators or attackers do it for you.
Top Cyber Risks for Financial Services Businesses
Regulations That Apply to Financial Services Firms
Five overlapping frameworks may apply to your firm depending on business type, state of incorporation, client base, and payment processing. Not all apply to every firm — use this guide to identify which are relevant to you.
FTC Safeguards Rule (16 CFR Part 314)
Applies to: All financial institutions under FTC jurisdiction: RIAs, mortgage brokers, insurance agents, credit unions, tax preparers, payday lenders, check-cashing firms, car dealers financing in-house.
- Written Information Security Plan (WISP) — must be maintained and updated annually
- Designated "Qualified Individual" overseeing the security program (can be external)
- Multi-factor authentication (MFA) for all internal systems accessing customer data
- Encryption of all customer data at rest and in transit
- Annual penetration testing; quarterly vulnerability scans
- Inventory of covered data and where it is stored, processed, transmitted
- Incident response plan with 72-hour notification to FTC for covered incidents
- Oversight of all service providers with access to customer data (contractual + monitoring)
NY DFS 23 NYCRR 500
Applies to: Covered entities: businesses operating under a DFS license in New York — includes insurance companies, banks, money transmitters, virtual currency businesses, and mortgage brokers originating in NY.
- Cybersecurity Program with annual CISO approval and board reporting
- Annual penetration testing and bi-annual vulnerability assessments
- MFA required for all internal access; privilege access management for admin accounts
- Encryption of Nonpublic Information (NPI) at rest and in transit
- Data retention schedule — only keep what is necessary
- Class A for large entities (>$10M gross revenue or 1,000 employees): requires independent CISO audit
- 72-hour notification to NY DFS Superintendent for cybersecurity events
- Affiliate and third-party oversight under the program
GLBA (Gramm-Leach-Bliley Act)
Applies to: All financial institutions — this is the foundational federal law. FTC Safeguards Rule is GLBA's implementing regulation. State attorneys general can also enforce GLBA.
- Financial Privacy Rule: disclose what data you collect, how you use it, and how you protect it
- Safeguards Rule: implement measures to protect customer NPI — now explicitly includes specific technical controls under the 2023 amendment
- Pretexting protection: procedures to prevent social engineering and phone-based fraud
- Disposal Rule: properly dispose of customer information when no longer needed
SOC 2 (for fintechs and RIAs with enterprise clients)
Applies to: Fintechs with B2B clients, RIAs serving institutional investors, and any firm where enterprise clients ask for a vendor security review. Not legally mandated but contractually required by most enterprise prospects.
- Trust Services Criteria: Security (required), Availability, Processing Integrity, Confidentiality, Privacy
- Common Criteria: CC1–CC7 (Control Environment through Monitoring)
- Continuous monitoring of controls — not a point-in-time checklist
- Annual audit by an independent CPA firm; Type II report covers 6+ months
- Evidence collection and retention for every control tested
PCI DSS (if accepting or processing card payments)
Applies to: Any firm that accepts, stores, processes, or transmits payment card data — regardless of size. Different self-assessment questionnaires (SAQs) apply based on how you accept cards.
- SAQ A (e-commerce/card-not-present): PCI DSS 4.0 requirements for merchants using hosted payment pages
- SAQ A-EP (e-commerce using redirect): additional scoping requirements for cardholder data flows
- Install and maintain network firewalls, change default passwords on all system components
- Encrypt cardholder data in transit with TLS 1.2+; at rest with strong cryptography
- Maintain inventory of all system components in scope; restrict access by business need-to-know
- Regularly test security systems and processes — at least annually and after significant changes
- Maintain information security policy and acceptable use documentation
Required Controls at a Glance
These controls appear across FTC Safeguards Rule, NY DFS 23 NYCRR 500, and GLBA — and are the basis for any compliance gap assessment.
| Control Area | Required Control |
|---|---|
| Access Control | MFA for all internal systems and admin accounts — FTC Safeguards Rule and NY DFS both require it |
| Encryption | TLS 1.2+ in transit; AES-256 or equivalent at rest for all customer NPI and card data |
| Incident Response | Written IR plan with 72-hour notification obligations to FTC and/or NY DFS; annual tabletop exercises |
| Third-Party Risk | Written contracts with all service providers requiring security standards; annual vendor risk assessments |
| Vulnerability Management | Annual penetration testing + quarterly vulnerability scans; all critical/high findings remediated within 30 days |
| Asset Inventory | Maintain a current inventory of all systems storing, processing, or transmitting customer data |
| Monitoring | Log collection, anomaly detection, and alerting for all systems accessing customer data — at minimum 90-day log retention |
| Security Awareness | Annual cybersecurity training for all employees; phishing simulations at least quarterly |
Frequently Asked Questions
Take Action
Your next steps — all free, no account required to start.
CyberStackHub Tools for Financial Services
These tools are most relevant for financial services businesses based on your sector's specific risk profile and compliance requirements.
Financial Services Cybersecurity Statistics
Data from public sources including Verizon DBIR, IBM Cost of Data Breach, FBI IC3, and industry-specific research.