GLBA Gramm-Leach-Bliley Act for financial institution privacy

version
0.1.0
GitHub stars
436

Install

/plugin install glba@grc-engineering-suite

Run it inside Claude Code after adding the marketplace with /plugin marketplace add GRCEngClub/claude-grc-engineering.

Contents

Discovered from source

Skills 1

GLBA Expert

Deep expertise in the Gramm-Leach-Bliley Act (GLBA) for financial institutions and their service providers.

Expertise Areas

GLBA Overview

Full Name: Gramm-Leach-Bliley Financial Services Modernization Act of 1999 Authority: 15 U.S.C. 6801-6809 Also Known As: Financial Modernization Act, GLBA Purpose: Protect consumers' personal financial information held by financial institutions

Regulatory Framework:

  • Federal Trade Commission (FTC): 16 CFR Part 313 (Privacy), 16 CFR Part 314 (Safeguards)
  • Banking Regulators: OCC, FDIC, Federal Reserve, NCUA (banks, credit unions)
  • Securities and Exchange Commission (SEC): Broker-dealers, investment advisors
  • State Insurance Commissioners: Insurance companies
  • CFTC: Commodity futures, derivatives

Effective Dates:

  • Original Act: November 12, 1999
  • Privacy Rule: July 1, 2001
  • Safeguards Rule: May 23, 2003
  • Amended Safeguards Rule: December 9, 2021 (compliance June 9, 2023)

Who Must Comply

"Financial Institution" Definition: Any institution engaged in "financial activities"

Covered Entities:

  1. Depository Institutions:

    • Commercial banks
    • Savings banks
    • Credit unions
    • Thrifts
  2. Securities Firms:

    • Broker-dealers
    • Investment advisors
    • Investment companies (mutual funds)
    • Transfer agents
  3. Insurance Companies:

    • Life insurance
    • Property and casualty insurance
    • Insurance agents and brokers
  4. Other Financial Services:

    • Mortgage lenders and brokers
    • Payday lenders
    • Finance companies
    • Collection agencies
    • Check cashing services
    • Wire transfer services
    • Tax preparation services (if offer RALs)
    • Real estate appraisers
    • Courier services (financial documents)
    • Credit counselors
    • Career counseling for finance jobs

FTC Jurisdiction: Financial institutions NOT regulated by banking/securities/insurance regulators

Service Providers: Must contractually commit to safeguarding customer information

Three Main Components

1. Financial Privacy Rule (16 CFR Part 313):

  • Requires privacy notices
  • Gives consumers opt-out rights
  • Restricts information sharing

2. Safeguards Rule (16 CFR Part 314):

  • Requires written information security program
  • Mandates specific security controls
  • Enforces vendor management

3. Pretexting Provisions (15 U.S.C. 6821):

  • Prohibits obtaining customer information under false pretenses
  • Requires institutions to protect against pretexting

Safeguards Rule (16 CFR Part 314)

Overview

Requirement: Develop, implement, and maintain comprehensive written information security program

Standard: "Administrative, technical, and physical safeguards" that are "appropriate" to size, complexity, nature, and scope of activities

Coverage: Protects "customer information" (current and former customers)

December 2021 Amendments

Major Changes:

  1. Encryption of customer information at rest and in transit (new)
  2. Multi-factor authentication for remote access (new)
  3. Qualified Individual designation requirement (enhanced)
  4. Annual board reporting (new)
  5. Written incident response plan (enhanced)
  6. Risk assessment requirement (clarified)
  7. Service provider oversight (enhanced)
  8. Security awareness training (new)
  9. Monitoring and testing requirements (enhanced)

Compliance Deadline: June 9, 2023

Reason for Update: Modernize rule for current cyber threats, align with banking regulator standards

Nine Required Elements

1. Designate Qualified Individual

Requirement: Appoint qualified individual to oversee information security program

Qualifications:

  • Knowledge and expertise appropriate to institution's size, complexity, activities
  • May be employee or service provider
  • Title doesn't matter (CISO, CIO, IT Director, consultant)

Responsibilities:

  • Oversee development, implementation, maintenance of security program
  • Report to board of directors (or equivalent) at least annually
  • Coordinate security functions across organization

Small Institution Flexibility: Qualified individual can have other responsibilities

2. Risk Assessment

Requirement: Written risk assessment identifying reasonably foreseeable internal and external threats

Assessment Scope:

  • Internal threats: Employees, contractors, processes, systems
  • External threats: Cyberattacks, environmental, third-party failures
  • Information covered: Customer information in all forms (electronic, paper)
  • Systems: All systems that collect, process, store, or transmit customer information

Assessment Process:

  1. Identify information assets
  2. Identify threats to those assets
  3. Identify vulnerabilities
  4. Assess likelihood of threat exploitation
  5. Assess potential impact
  6. Evaluate existing safeguards
  7. Determine residual risk
  8. Prioritize risks

Frequency: Periodically (at least annually recommended) and when significant changes

3. Design and Implement Safeguards

Requirement: Design and implement safeguards to control risks identified in risk assessment

Safeguard Types:

Administrative:

  • Security policies and procedures
  • Security governance structure
  • Access control policies
  • Acceptable use policies
  • Change management procedures
  • Vendor management program

Technical:

  • Encryption (at rest and in transit)
  • Multi-factor authentication
  • Access controls (RBAC, least privilege)
  • Network security (firewalls, IDS/IPS)
  • Endpoint protection
  • Logging and monitoring
  • Secure development practices
  • Vulnerability management

Physical:

  • Facility access controls
  • Visitor management
  • Secure disposal procedures
  • Environmental controls
  • Media handling

Tailored Approach: Safeguards appropriate to institution's size, complexity, nature, and scope

4. Monitor and Test Effectiveness

Requirement: Regularly monitor and test effectiveness of safeguards

Monitoring:

  • Continuous security monitoring
  • Log review and analysis
  • Anomaly detection
  • Security metrics tracking
  • Compliance monitoring

Testing:

  • Vulnerability scanning: Quarterly or more frequent
  • Penetration testing: Annual or risk-based
  • Security control testing: Ongoing
  • Incident response plan testing: Annual
  • Business continuity/disaster recovery testing: Annual

Frequency: Continuous monitoring; testing at least annually or upon significant changes

Testing Depth: Based on institution's risk assessment

5. Train Personnel

Requirement: Provide regular security awareness training to personnel

Audience: All personnel (not just IT)

Training Content:

  • Security risks and responsibilities
  • How to identify and report security incidents
  • Phishing and social engineering awareness
  • Password security
  • Physical security procedures
  • Clean desk policies
  • Acceptable use of systems
  • Privacy obligations

Frequency:

  • Upon hiring
  • At least annually
  • When policies/threats change

Documentation: Maintain training records (attendance, completion, test scores)

6. Vendor Management (Service Providers)

Requirement: Exercise due diligence in selecting service providers and require them by contract to implement appropriate safeguards

Service Provider Definition: Entity that receives, maintains, processes, or has access to customer information on behalf of financial institution

Examples:

  • Cloud service providers (AWS, Azure, Google Cloud)
  • SaaS vendors (Salesforce, Workday)
  • Payment processors
  • Core banking system vendors
  • IT managed service providers
  • Document storage providers
  • Shredding services

Due Diligence Requirements:

  1. Risk-based assessment of service provider's security posture
  2. Review certifications (SOC 2, ISO 27001, etc.)
  3. Security questionnaires or audits
  4. Financial stability review
  5. References from other customers

Contract Requirements:

  • Implement and maintain appropriate safeguards
  • Protect confidentiality and integrity of customer information
  • Permit institution to monitor/audit service provider's security
  • Notify institution of security incidents
  • Return or securely destroy customer information upon contract termination

Ongoing Oversight:

  • Periodic reviews (annual recommended)
  • Monitor for security incidents
  • Review SOC 2 reports or equivalent
  • Audit compliance with contract terms
  • Reassess risk periodically

7. Evaluate and Adjust Program

Requirement: Evaluate and adjust information security program based on results of monitoring, testing, and changes to environment

Evaluation Triggers:

  • Results of testing and monitoring
  • Material changes to operations or business arrangements
  • Changes to information systems or technology
  • Results of risk assessments
  • Security incidents (actual or industry-wide)
  • Changes to threats/vulnerabilities

Adjustment Process:

  1. Review current safeguards effectiveness
  2. Identify gaps or weaknesses
  3. Update risk assessment
  4. Implement new/modified safeguards
  5. Update policies and procedures
  6. Train personnel on changes

Documentation: Maintain records of program updates and rationale

8. Incident Response Plan

Requirement: Written incident response plan

Plan Components:

1. Incident Response Team:

  • Roles and responsibilities
  • Contact information
  • Escalation procedures

2. Incident Detection and Analysis:

  • Monitoring and alerting mechanisms
  • Incident classification criteria
  • Analysis procedures

3. Containment, Eradication, Recovery:

  • Containment strategies (short-term, long-term)
  • Eradication procedures
  • Recovery and restoration procedures

4. Post-Incident Activities:

  • Lessons learned process
  • Root cause analysis
  • Evidence preservation
  • Reporting and documentation

Notification Procedures:

  • Internal escalation
  • Customer notification (per state breach laws)
  • Regulatory notification (if required)
  • Law enforcement (if criminal)
  • Credit bureaus (if identity theft risk)

Testing: Test incident response plan at least annually

Updating: Revise plan based on testing results, incidents, and changes

9. Encryption

Requirement: Encrypt customer information in transit over external networks and at rest

Encryption in Transit:

  • TLS 1.2+ for web traffic
  • SFTP/FTPS for file transfers
  • Encrypted email (S/MIME, PGP) for sensitive data
  • VPN for remote access
  • Encrypted APIs

Encryption at Rest:

  • Database encryption (TDE or column-level)
  • Full disk encryption for endpoints
  • File-level encryption for sensitive documents
  • Encrypted backups
  • Cloud storage encryption

Key Management:

  • Secure key generation
  • Key storage (HSM or key vault)
  • Key rotation
  • Access controls on keys
  • Key backup/recovery

Exceptions: Encryption not required if compensating controls provide equivalent protection AND documented in risk assessment

Compensating Controls Examples:

  • Isolated network segments
  • Strong physical security
  • Tokenization
  • Data masking

Exception Documentation:

  • Justification for exception
  • Description of compensating controls
  • Residual risk acceptance
  • Periodic review of exception

Multi-Factor Authentication (MFA)

Requirement: Implement MFA or another method providing equivalent or more secure access control

Scope: Any individual accessing customer information on institution's information systems

Applicability:

  • Remote access (required)
  • Local access (risk-based but recommended)
  • Privileged accounts (highly recommended)

MFA Types:

  • Something you know + Something you have: Password + hardware token, mobile app
  • Something you know + Something you are: Password + biometric
  • Something you have + Something you are: Hardware token + biometric

Acceptable MFA Methods:

  • Hardware tokens (YubiKey, RSA SecurID)
  • Mobile authenticator apps (Google Authenticator, Microsoft Authenticator, Duo)
  • Push notifications (Duo Push, Okta Verify)
  • Biometrics + password
  • Smart cards

Unacceptable MFA:

  • SMS-based OTP (acceptable for low-risk but not recommended)
  • Email-based OTP (not MFA)
  • Security questions (not MFA)

Exceptions: Risk-based determination if MFA not feasible (document in risk assessment)

Alternative Access Controls:

  • Risk-based authentication
  • Behavioral analytics
  • Isolated networks with strong physical controls

Annual Board Reporting

Requirement: Qualified Individual reports to board of directors (or equivalent) at least annually

Report Content:

  1. Overall status of information security program
  2. Compliance with Safeguards Rule
  3. Material matters related to security program (incidents, significant changes, risks)
  4. Risk assessment summary
  5. Testing and monitoring results
  6. Service provider oversight status
  7. Incidents and response effectiveness
  8. Budget and resources for security program
  9. Recommendations for program improvements

Board Definition: Board of directors, committee of board, or senior officer (if no board)

Frequency: At least annually; more often if material incidents/changes

Documentation: Maintain records of board presentations and approval

Small Institution Flexibility: Report to senior management if no formal board

Compliance Deadlines

Effective Date: June 9, 2023 (for FTC-regulated institutions)

Banking Regulator Timelines: Vary by regulator; many already compliant with similar requirements

Privacy Rule (16 CFR Part 313)

Overview

Purpose: Give consumers transparency and control over financial institution's use of their personal information

Coverage: "Nonpublic personal information" (NPI) of consumers and customers

Key Requirements:

  1. Provide initial privacy notice
  2. Provide annual privacy notice (if required)
  3. Allow consumers to opt-out of certain information sharing
  4. Comply with consumer opt-out directions

Customer vs. Consumer

Consumer: Individual who obtains or has obtained financial product/service for personal, family, or household purposes

Customer: Consumer with continuing relationship with financial institution

Distinction Matters:

  • Initial notice: Required for both consumers and customers
  • Annual notice: Required only for customers (with exceptions)
  • Opt-out: Required for both consumers and customers

Nonpublic Personal Information (NPI)

Definition: Personally identifiable financial information not publicly available

Examples:

  • Name, address, SSN, income, credit score
  • Account numbers, balances
  • Transaction history
  • Information from application forms
  • Information from consumer reports
  • Information from other institutions

NOT NPI:

  • Information lawfully available to general public (phone directories, government records)
  • De-identified/aggregated information

Privacy Notice Requirements

Initial Privacy Notice:

  • When: Before establishing customer relationship or before disclosing NPI to nonaffiliated third party
  • To Whom: All consumers (includes customers)
  • Content: All required elements (information practices, opt-out rights, etc.)

Annual Privacy Notice:

  • When: At least once in 12-month period
  • To Whom: Customers only (continuing relationship)
  • Exception: Not required if only share under exceptions (service providers, affiliates) and haven't changed practices

Revised Privacy Notice:

  • When: Before implementing material changes to privacy practices
  • To Whom: Affected consumers/customers
  • Content: Describe changes

Required Content (All Notices):

  1. Categories of NPI collected
  2. Categories of NPI disclosed
  3. Categories of affiliates/third parties to whom disclosed
  4. Policies/practices to protect information
  5. Categories of information disclosed (even if under exceptions)
  6. Opt-out information (if applicable)
  7. How to exercise opt-out rights
  8. Explanation of exceptions under Sections 313.14/313.15

Clear and Conspicuous: Reasonably understandable and designed to call attention

Model Privacy Form: FTC provides optional model form (safe harbor if used correctly)

Information Sharing and Opt-Out

Opt-Out Required When:

  • Sharing NPI with nonaffiliated third parties
  • Sharing beyond exceptions (service providers, joint marketing, legal compliance)

Opt-Out NOT Required When:

  • Sharing with affiliates (but FCRA notice may be required)
  • Sharing with service providers (with confidentiality contract)
  • Sharing under joint marketing agreements
  • Sharing as permitted by law
  • Sharing to process transactions customer requested
  • Sharing to service/maintain accounts
  • Sharing to prevent fraud
  • Sharing with consumer reporting agencies
  • Sharing in connection with sale/merger

Opt-Out Mechanism:

  • Reasonable means (online, phone, mail)
  • Free of charge
  • Response time: Reasonable period (30 days standard)
  • Duration: Until consumer revokes (no expiration required)

Reuse and Redisclosure:

  • If receive NPI under exception, can only use for that purpose
  • Cannot redisclose except back to institution or under same exception

Account Number Restrictions

Prohibition: Cannot disclose account number or access code for credit card, deposit, or transaction account to nonaffiliated third party for marketing purposes

Exceptions:

  • To consumer reporting agencies
  • To service providers performing marketing for institution
  • To participant in private label/affinity card program
  • To agent/service provider solely to verify account accuracy

No Opt-Out: Prohibition is absolute; opt-out not sufficient

State Law Preemption

General Rule: GLBA preempts state laws only to extent inconsistent

Greater Protection: States can provide MORE privacy protection (not less)

Examples:

  • Vermont: Opt-in required for sharing with data brokers
  • California: CCPA/CPRA additional requirements
  • Massachusetts: 201 CMR 17.00 data security requirements
  • New York: NYDFS 23 NYCRR 500 cybersecurity regulation

Compliance Strategy: Meet GLBA + strictest applicable state law

Pretexting Provisions

Overview

Prohibition: Obtaining customer information from financial institution under false, fictitious, or fraudulent pretenses

Authority: 15 U.S.C. 6821

Criminal Penalties:

  • Fines up to $250,000 for individuals
  • Imprisonment up to 5 years
  • Fines up to $500,000 for organizations

What is Pretexting

Definition: Using false pretenses to obtain customer information

Examples:

  • Posing as customer to obtain account information
  • Posing as institution employee to trick customer service
  • Using stolen credentials to access customer data
  • Social engineering to extract information
  • Phishing for customer information

Prohibited Actions:

  • Use false statements or documents
  • Impersonate customer or institution
  • Use fraudulent statements to persuade disclosure
  • Use stolen or forged documents

Institution Responsibilities

Prevention Requirements:

  • Implement administrative, technical, and physical safeguards
  • Authenticate callers before releasing information
  • Train employees to recognize pretexting attempts
  • Procedures to verify third-party requests
  • Monitor for suspicious activity

Safeguards:

  • Multi-factor authentication before releasing information
  • Call-back verification procedures
  • Challenge questions
  • Documented authorization for third-party requests
  • Employee training on social engineering

Reporting: Report suspected pretexting to law enforcement and appropriate regulators

Regulatory Enforcement

Federal Trade Commission (FTC)

Jurisdiction: Financial institutions not regulated by banking, securities, or insurance regulators

Examples:

  • Mortgage brokers
  • Payday lenders
  • Check cashing services
  • Collection agencies
  • Tax preparers
  • Career counselors

Enforcement Actions:

  • Administrative complaints
  • Civil penalties up to $50,120 per violation per day (adjusted for inflation)
  • Injunctive relief
  • Compliance monitoring
  • Consumer redress

Recent FTC Enforcement Examples:

Drizly (2022): $2.5M penalty

  • Inadequate data security despite Safeguards Rule requirements
  • Failure to implement MFA
  • Poor vendor oversight
  • CEO held personally liable

Chegg (2022): Settlement

  • Four data breaches due to poor security
  • Misleading privacy claims
  • Failed to implement basic safeguards
  • 20-year compliance monitoring

PayPal/Venmo (2018): Settlement

  • Misleading privacy claims about Venmo default settings
  • Inadequate privacy notice disclosures

TaxSlayer (2017): Settlement

  • Data breach due to inadequate security
  • Failed to implement multi-factor authentication
  • Inadequate employee training
  • Weak password policies

Banking Regulators

OCC, FDIC, Federal Reserve, NCUA: Regulate banks and credit unions

Standards: Similar to FTC Safeguards Rule but often more detailed

  • FFIEC Guidelines: Comprehensive security guidance
  • Interagency Guidelines: 12 CFR Part 30 Appendix B (OCC), similar for others
  • Higher Standards: Banks subject to additional requirements beyond GLBA

Enforcement:

  • Cease and desist orders
  • Civil money penalties
  • Consent orders
  • Safety and soundness examinations
  • Compliance examinations

SEC and State Insurance Commissioners

SEC: Regulates broker-dealers, investment advisors, investment companies

  • Regulation S-P: SEC's privacy and safeguards rule (similar to GLBA)
  • Enforcement: Administrative proceedings, penalties, injunctions

State Insurance Regulators: Regulate insurance companies

  • Model Privacy Act: Many states adopted NAIC model
  • Enforcement: State-level actions, license revocation

Common Compliance Challenges

1. Encryption Implementation

Challenge: Legacy systems can't support encryption

Solutions:

  • Network segmentation to isolate legacy systems
  • Encryption gateways
  • Migrate to modern systems
  • Document as exception with compensating controls

Example Compensating Controls:

  • Physical isolation of legacy systems
  • Strict access controls
  • Enhanced monitoring
  • Acceptable only with documented risk acceptance

2. Multi-Factor Authentication Deployment

Challenge: User resistance, technology limitations

Solutions:

  • Phased rollout (start with remote access, then privileged accounts)
  • User training on benefits
  • Select user-friendly MFA (push notifications, biometrics)
  • Risk-based authentication for low-risk access

Common MFA Pitfalls:

  • SMS-based OTP (vulnerable to SIM swapping)
  • No MFA for privileged accounts (highest risk)
  • No backup authentication method

3. Vendor Management at Scale

Challenge: Hundreds of vendors, limited resources

Solutions:

  • Tiered approach: Categorize vendors by risk level
    • Tier 1 (High Risk): Access to customer data, critical systems - full assessment
    • Tier 2 (Medium Risk): Limited access - questionnaire, certifications
    • Tier 3 (Low Risk): No customer data access - minimal assessment
  • Standardized contracts: Template agreements with security requirements
  • Vendor risk platforms: Automate vendor assessments (SecurityScorecard, BitSight)
  • Accept certifications: SOC 2 Type II, ISO 27001 in lieu of detailed assessment

4. Resource Constraints (Small Institutions)

Challenge: Limited budget, no dedicated security staff

Solutions:

  • Outsource to MSSP: Managed security services for monitoring, incident response
  • Cloud-first approach: Leverage AWS, Azure, Google Cloud built-in security
  • Commercial products: Use turnkey solutions (Microsoft 365 E5, Google Workspace Enterprise)
  • Qualified individual: Hire part-time consultant or fractional CISO
  • Simplified documentation: Use templates, focus on critical controls

Cost-Effective Controls:

  • Microsoft 365 E3/E5 (MFA, encryption, DLP)
  • Cloud-based firewalls (Cisco Meraki, Palo Alto Prisma)
  • Endpoint protection (CrowdStrike, SentinelOne)
  • Security awareness (KnowBe4, Proofpoint)

5. Board Reporting

Challenge: Board lacks technical expertise, unclear what to report

Solutions:

  • Business language: Avoid jargon, focus on business impact
  • Metrics-driven: Use dashboards and KPIs
    • Number of incidents
    • Mean time to detect/respond
    • Vulnerability remediation rates
    • Training completion rates
    • Audit findings
  • Risk-based: Quantify risk in financial terms
  • Benchmarking: Compare to industry standards
  • Actionable: Include recommendations with budget/resource needs

Sample Board Report Outline:

  1. Executive Summary (1 page)
  2. Program Status (compliant vs. gaps)
  3. Risk Summary (top 5 risks)
  4. Incidents (count, severity, response)
  5. Testing Results (vulnerabilities, penetration tests)
  6. Vendor Oversight (high-risk vendor status)
  7. Metrics and Trends (year-over-year)
  8. Budget and Resources (current vs. needed)
  9. Recommendations (investments, policy changes)

6. Privacy Notice Delivery

Challenge: Ensuring electronic delivery compliance, notice fatigue

Solutions:

  • E-SIGN compliance: Obtain affirmative consent for electronic delivery
  • Multi-channel: Offer choice of paper or electronic
  • Clear opt-out: Make opt-out prominent and easy
  • Test delivery: Ensure emails not filtered as spam
  • Annual notice exception: Many institutions exempt under FAST Act (if only share under exceptions)

Annual Notice Exception Criteria:

  1. Only share with service providers or for joint marketing
  2. Haven't changed privacy policies
  3. No sharing with nonaffiliates beyond exceptions

If Exempt: No annual notice required, but must still provide initial and revised notices

Integration with Other Regulations

GLBA + HIPAA

Business Associates:

  • Healthcare providers subject to both HIPAA and GLBA
  • Mental health providers who process payments
  • Compliance: Meet both HIPAA Security Rule and GLBA Safeguards Rule

Harmonization:

  • Both require risk assessments
  • Both require encryption
  • Both require training
  • Both require vendor management
  • GLBA Safeguards Rule can satisfy many HIPAA Security Rule requirements

GLBA + PCI DSS

Payment Card Data:

  • Financial institutions processing credit cards subject to both GLBA and PCI DSS
  • Cardholder data (PCI) vs. Customer information (GLBA): Overlapping but distinct

Harmonization:

  • PCI DSS encryption requirements align with GLBA
  • PCI DSS access controls align with GLBA
  • Both require incident response plans
  • Both require vendor management
  • PCI DSS more prescriptive; GLBA more flexible

GLBA + State Privacy Laws

CCPA/CPRA (California):

  • CCPA exemption: GLBA-covered data exempt from CCPA if institution in compliance
  • CPRA: Narrowed exemption; some CCPA requirements still apply

Vermont Data Broker Law:

  • Opt-in required for sale of customer information to data brokers
  • Stricter than GLBA opt-out

State Breach Notification Laws:

  • All 50 states have breach notification laws
  • GLBA requires safeguards but not always notification
  • Must comply with state breach laws in addition to GLBA

GLBA + NYDFS Cybersecurity Regulation

New York Financial Services Firms:

  • Subject to both GLBA and NYDFS 23 NYCRR 500

NYDFS More Stringent:

  • Annual certification required (CISO signature)
  • Penetration testing (annual)
  • Multi-factor authentication (required)
  • Encryption (required)
  • Incident response plan (72-hour reporting)

Compliance Strategy: Meet NYDFS requirements (will exceed GLBA)

Best Practices

Risk-Based Approach

Core Principle: Tailor safeguards to institution's size, complexity, and risk

Considerations:

  • Size: Small institutions can use simpler controls
  • Complexity: Complex organizations need enterprise solutions
  • Data sensitivity: More sensitive data requires stronger controls
  • Threat landscape: Higher-risk industries (banking) need advanced defenses

Documentation: Document risk-based decisions in risk assessment

Defense in Depth

Strategy: Layer multiple controls so if one fails, others provide protection

Layers:

  1. Perimeter: Firewalls, IDS/IPS
  2. Network: Segmentation, access controls
  3. Endpoint: Antivirus, EDR, encryption
  4. Application: Secure coding, WAF
  5. Data: Encryption, DLP, tokenization
  6. Physical: Access controls, surveillance
  7. Policies: Training, awareness, governance

Continuous Improvement

Mindset: Security is ongoing process, not one-time project

Activities:

  • Annual risk assessments
  • Quarterly vulnerability scans
  • Annual penetration tests
  • Annual incident response drills
  • Ongoing training
  • Continuous monitoring
  • Regular policy reviews
  • Post-incident lessons learned

Feedback Loop: Use findings to improve program

Vendor Risk Management Framework

Lifecycle Approach:

  1. Selection: Due diligence, security assessment
  2. Contracting: Security requirements in contract
  3. Onboarding: Validate security controls before go-live
  4. Ongoing Monitoring: Annual reviews, SOC 2 reports, incident monitoring
  5. Offboarding: Secure data return/destruction

Risk Tiers:

  • Critical: Direct access to customer data, critical systems
  • High: Indirect access, important but not critical
  • Medium: Limited access, standard business vendors
  • Low: No access to systems/data, commodity services

Tiered Assessment:

  • Critical: Detailed assessment, annual reviews, SOC 2 required
  • High: Questionnaire, certifications, biennial reviews
  • Medium: Basic questionnaire, one-time assessment
  • Low: Contract terms only, no assessment

Resources

Official Sources:

  • FTC: ftc.gov/tips-advice/business-center/privacy-and-security/gramm-leach-bliley-act
  • 16 CFR Part 313: Privacy Rule full text
  • 16 CFR Part 314: Safeguards Rule full text
  • FTC Business Guidance: "Safeguards Rule: What Your Business Needs to Know"
  • FTC Small Business Guide: "Data Security Made Simpler"

Industry Resources:

  • FFIEC: Federal Financial Institutions Examination Council guidance
  • NIST: Cybersecurity Framework, SP 800-53, SP 800-171
  • CIS Controls: Center for Internet Security baseline controls
  • SANS: Security awareness training resources

Capabilities

  • GLBA compliance assessment and gap analysis
  • Safeguards Rule implementation (all nine elements)
  • Privacy Rule compliance (notices, opt-out, sharing practices)
  • Risk assessment methodology and execution
  • Information security program development
  • Policy and procedure writing
  • Encryption implementation guidance
  • Multi-factor authentication deployment
  • Vendor management program design
  • Incident response plan development
  • Security awareness training programs
  • Board reporting and governance
  • FTC enforcement action analysis
  • Integration with HIPAA, PCI DSS, state laws
  • Cost-benefit analysis for security investments
  • Remediation roadmaps and project planning

Commands 5

GLBA Compliance Assessment

Evaluates organizational readiness for Gramm-Leach-Bliley Act (GLBA) compliance.

Arguments

  • $1 - Assessment scope (required: full, safeguards, privacy, pretexting)
  • $2 - Institution type (optional: bank, credit-union, securities-firm, insurance-company, other)

GLBA Overview

Authority: 15 U.S.C. 6801-6809 Enforced by: FTC, OCC, FDIC, Federal Reserve, NCUA, SEC, state regulators Effective: 1999, with ongoing amendments Purpose: Protect consumer financial privacy and secure financial information

GLBA Components

Safeguards Rule (16 CFR Part 314)

Requirement: Develop, implement, and maintain comprehensive information security program Applies to: Financial institutions handling customer information Updated: December 2021 (effective June 2023)

Nine Elements Required:

  1. Risk assessment
  2. Security systems design and implementation
  3. Access controls and authorization
  4. Encryption of customer information at rest and in transit
  5. Multi-factor authentication (MFA)
  6. Security awareness training
  7. Incident response plan
  8. Vendor/service provider oversight
  9. Annual reporting to board of directors

Privacy Rule (16 CFR Part 313)

Requirement: Provide clear privacy notices to consumers Key Elements:

  • Initial privacy notice at account opening
  • Annual privacy notice (opt-out required if sharing with non-affiliates)
  • Opt-out rights for certain information sharing
  • Redelivery of notices after material changes

Pretexting Protection (15 U.S.C. 6821)

Prohibition: Obtaining customer information under false pretenses Requirements: Administrative, technical, and physical safeguards

Assessment Scope Options

Full Assessment

Comprehensive evaluation across all three GLBA components:

  • Safeguards Rule compliance
  • Privacy Rule implementation
  • Pretexting prevention controls

Safeguards-Only Assessment

Focused on information security program:

  • Nine required elements evaluation
  • Technical controls review
  • Vendor management assessment

Privacy-Only Assessment

Privacy notice and opt-out compliance:

  • Notice delivery and content
  • Opt-out mechanisms
  • Sharing practices review

Pretexting Assessment

Social engineering and fraud prevention:

  • Authentication procedures
  • Employee training
  • Identity verification controls

Institution Types

TypeExamplesPrimary Regulator
BanksCommercial banks, savings banksOCC, FDIC, Federal Reserve
Credit UnionsFederal/state credit unionsNCUA
Securities FirmsBroker-dealers, investment advisorsSEC
Insurance CompaniesLife, property, casualty insurersState insurance commissioners
OtherMortgage brokers, collection agencies, tax preparersFTC

Assessment Output

  1. Compliance Score: Overall GLBA readiness percentage
  2. Safeguards Rule Status:
    • Nine required elements implementation
    • Technical controls maturity
    • Encryption coverage
    • MFA deployment
    • Training program effectiveness
    • Incident response capability
    • Vendor management rigor
    • Board reporting status
  3. Privacy Rule Status:
    • Privacy notice accuracy and completeness
    • Delivery mechanisms
    • Opt-out process functionality
    • Information sharing practices
  4. Pretexting Protection:
    • Authentication strength
    • Social engineering defenses
    • Employee awareness
  5. Regulatory Risk Assessment:
    • Enforcement action likelihood
    • Gap severity analysis
  6. Remediation Roadmap:
    • Prioritized action plan
    • Quick wins vs. long-term initiatives
    • Resource requirements
    • Timeline estimates

Key Requirements by Rule

Safeguards Rule Requirements

Risk Assessment:

  • Identify reasonably foreseeable internal/external threats
  • Assess likelihood and potential damage
  • Evaluate existing safeguards effectiveness

Security Program Elements:

  • Designated qualified individual (CISO or equivalent)
  • Written information security plan
  • Access controls and authorization
  • Encryption at rest and in transit (customer information)
  • Multi-factor authentication for remote access
  • Secure development practices
  • Security awareness training
  • Incident response plan
  • Service provider oversight
  • Annual board reporting

Technical Controls:

  • Network security (firewalls, segmentation)
  • Endpoint protection
  • Data loss prevention
  • Logging and monitoring
  • Vulnerability management
  • Penetration testing (risk-based)

Privacy Rule Requirements

Privacy Notice Content:

  • Information collected
  • How information is shared
  • How information is protected
  • Consumer rights to opt-out
  • Contact information

Delivery Requirements:

  • Initial notice at customer relationship establishment
  • Annual notice (if required)
  • Notice of material changes
  • Clear and conspicuous delivery

Opt-Out Requirements:

  • Reasonable means to opt-out (online, phone, mail)
  • 30-day minimum opt-out period
  • Honor opt-out requests
  • Reaffirmation for expired opt-outs

Pretexting Protection

Prevention Measures:

  • Customer authentication before releasing information
  • Employee training on social engineering
  • Verification procedures for third-party requests
  • Incident reporting for suspected pretexting

Common Compliance Gaps

  1. Encryption:

    • Customer information not encrypted at rest
    • Transmission encryption gaps (email, file transfers)
    • Inadequate key management
  2. Multi-Factor Authentication:

    • Not deployed for remote access
    • SMS-based MFA (inadequate for high-risk scenarios)
    • No MFA for privileged accounts
  3. Risk Assessment:

    • Not performed or outdated
    • Missing threat analysis
    • No assessment of safeguards effectiveness
  4. Vendor Management:

    • No due diligence process
    • Contracts lack security requirements
    • No ongoing monitoring
  5. Incident Response:

    • No written IR plan
    • Plan not tested
    • No notification procedures
  6. Privacy Notices:

    • Outdated or inaccurate
    • Not delivered annually
    • Opt-out mechanisms broken
  7. Board Reporting:

    • Security not reported to board
    • No annual certification
    • Insufficient detail

FTC Enforcement Focus Areas

Recent Enforcement Actions:

  • Inadequate data security (e.g., Drizly, Chegg)
  • Failure to implement MFA
  • Lack of encryption
  • Insufficient vendor oversight
  • Misleading privacy statements

Penalties:

  • Civil penalties up to $50,000+ per violation per day
  • Individual liability for officers/directors
  • Compliance monitoring requirements
  • Reputational damage

Examples

# Full GLBA assessment for commercial bank
/glba:assess full bank

# Safeguards Rule assessment only
/glba:assess safeguards credit-union

# Privacy Rule compliance check for broker-dealer
/glba:assess privacy securities-firm

# Pretexting controls for insurance company
/glba:assess pretexting insurance-company

GLBA Evidence Checklist

Generates comprehensive evidence collection checklists for Gramm-Leach-Bliley Act (GLBA) Safeguards Rule and Privacy Rule compliance for financial institutions.

Never commit evidence artifacts to source control. The outputs below include real usernames, credential reports, MFA device states, and privileged-account inventories. .gitignore covers evidence/ by default so git add -A will not sweep it up, but durable storage is your responsibility. Use an encrypted, access-controlled evidence locker (encrypted S3 with least-privilege IAM, a GRC platform, or a shared drive with full-disk encryption and MFA-gated access).

Usage

/glba:evidence-checklist <rule-section> [--institution-type <bank|broker|insurer>] [--export <format>]

Arguments

  • <rule-section>: GLBA section (e.g., "Safeguards Rule", "Privacy Rule", "§314.4(b)") or topic (e.g., "Information Security Program", "Customer Privacy Notices")
  • --institution-type: Type of financial institution (bank, broker, insurer, other). Default: bank
  • --export: Export format (json, csv, markdown). Default: markdown

Example: Safeguards Rule - Information Security Program Evidence

/glba:evidence-checklist "Safeguards Rule" --institution-type bank

Output:

GLBA Evidence Checklist
Regulation: Safeguards Rule (16 CFR Part 314)
Institution Type: Bank / Credit Union
Regulator: FTC (Federal Trade Commission) / FDIC / OCC / NCUA (depending on charter)
Effective Date: December 9, 2022 (amended rule)
Penalties: Up to $46,517 per violation per day

## Safeguards Rule Requirements

The Safeguards Rule requires financial institutions to develop, implement, and maintain a comprehensive information security program that contains administrative, technical, and physical safeguards to protect customer information.

### Core Requirements (§314.4)

1. **Qualified Individual** - Designate qualified individual to oversee information security program
2. **Risk Assessment** - Conduct periodic risk assessments
3. **Safeguards Design** - Design and implement safeguards to control identified risks
4. **Monitoring and Testing** - Regular monitoring and testing of safeguards
5. **Training** - Security awareness training for personnel
6. **Service Provider Oversight** - Due diligence and contractual protections for service providers
7. **Change Management** - Evaluate and adjust program based on monitoring, testing, changes
8. **Incident Response** - Written incident response plan
9. **Reporting to Board** - Annual report to board of directors or equivalent

## Evidence Requirements

### Required Documentation

□ **Written Information Security Program (WISP)**
  - Comprehensive documentation of information security program
  - Required elements per §314.4(a):
    - Designated Qualified Individual
    - Risk assessment procedures
    - Safeguards to control risks
    - Monitoring and testing program
    - Personnel training program
    - Service provider oversight
    - Change management procedures
    - Incident response plan
  - Update frequency: Annually or when material changes
  - Approver: Board of Directors or Senior Officer
  - Evidence: Board-approved WISP v1.x with meeting minutes

□ **Qualified Individual Designation**
  - Written designation of Qualified Individual (§314.4(a))
  - Name, title, qualifications
  - Responsibilities and authority
  - Evidence: Designation letter, organizational chart
  - Frequency: Annual review

□ **Risk Assessment (Annual)**
  - Comprehensive assessment of risks to customer information (§314.4(b))
  - Required elements:
    - Criteria for evaluating and categorizing identified security risks or threats
    - Criteria for assessing confidentiality, integrity, availability of customer information
    - Requirements describing how identified risks will be mitigated or accepted
    - Periodic risk assessments (at least annually)
  - Evidence: Annual Risk Assessment Report (signed by Qualified Individual)
  - Frequency: Annually minimum

□ **Safeguards Documentation (§314.4(c))**
  - Access controls (user authentication, access rights)
  - Encryption of customer information at rest (if feasible)
  - Encryption of customer information in transit
  - Secure development practices
  - Multi-factor authentication (MFA) for accessing customer information
  - Disposal procedures for customer information
  - Change management procedures
  - Evidence: Technical safeguards documentation, policies

□ **Monitoring and Testing Program (§314.4(d))**
  - Continuous monitoring or periodic penetration testing
  - Periodic vulnerability assessments (at least annually)
  - Annual penetration testing
  - Evidence: Monitoring dashboards, vulnerability scan reports, penetration test reports
  - Frequency: Continuous (monitoring), annually (vulnerability assessments + penetration tests)

□ **Personnel Training Program (§314.4(e))**
  - Security awareness training for all personnel
  - Required topics: Safeguards Rule requirements, customer information handling, incident reporting
  - Evidence: Training materials, completion records, attendance logs
  - Frequency: Annually, on hire for new employees

□ **Service Provider Oversight (§314.4(f))**
  - Due diligence before engaging service provider
  - Contracts requiring safeguards for customer information
  - Periodic assessments of service providers
  - Evidence: Service provider inventory, due diligence reports, contracts with security clauses
  - Frequency: Before engagement, annual review

□ **Incident Response Plan (§314.4(h))**
  - Written plan for responding to security events
  - Required elements:
    - Goals of incident response plan
    - Internal processes for responding to incidents
    - Clear roles, responsibilities, decision-making authority
    - External and internal communications and information sharing
    - Incident containment and mitigation
    - Documentation and reporting requirements
    - Evaluation and revision following incidents
  - Evidence: Incident Response Plan v1.x
  - Frequency: Annual review, update after incidents

□ **Annual Report to Board of Directors (§314.4(i))**
  - Written report to board (or equivalent) at least annually
  - Required content:
    - Overall status of information security program
    - Compliance with Safeguards Rule
    - Material matters related to program (risk assessment, assessments, incidents)
  - Evidence: Annual Board Report, Board meeting minutes acknowledging report
  - Frequency: Annually

### Automated Evidence Collection

✓ **Encryption at Rest Evidence (§314.4(c)(3))**
```bash
# AWS - S3 bucket encryption (customer data)
aws s3api list-buckets --output json | jq -r '.Buckets[].Name' | while read bucket; do
  encryption=$(aws s3api get-bucket-encryption --bucket "$bucket" 2>&1)
  if echo "$encryption" | grep -q "ServerSideEncryptionConfigurationNotFoundError"; then
    echo "$bucket,NOT ENCRYPTED" >> evidence/glba-s3-encryption-$(date +%Y%m%d).csv
  else
    echo "$bucket,ENCRYPTED" >> evidence/glba-s3-encryption-$(date +%Y%m%d).csv
  fi
done

# RDS encryption
aws rds describe-db-instances \
  --query 'DBInstances[].[DBInstanceIdentifier,StorageEncrypted,KmsKeyId]' \
  --output json > evidence/glba-rds-encryption-$(date +%Y%m%d).json

# EBS volumes (ensure customer data volumes encrypted)
aws ec2 describe-volumes \
  --filters "Name=tag:DataClassification,Values=CustomerInformation" \
  --query 'Volumes[].[VolumeId,Encrypted,KmsKeyId]' \
  --output json > evidence/glba-ebs-encryption-$(date +%Y%m%d).json

Collection Frequency: Monthly Retention: 5 years (typical financial services record retention) Purpose: Demonstrates encryption at rest per §314.4(c)(3)

✓ Encryption in Transit Evidence (§314.4(c)(4))

# Application Load Balancer - HTTPS enforcement
aws elbv2 describe-load-balancers --output json | \
  jq '.LoadBalancers[] | {Name: .LoadBalancerName, Scheme: .Scheme}' \
  > evidence/glba-alb-$(date +%Y%m%d).json

# Check for HTTP listeners (should redirect to HTTPS)
aws elbv2 describe-listeners --load-balancer-arn <ARN> | \
  jq '.Listeners[] | select(.Protocol == "HTTP" and .DefaultActions[].Type != "redirect")' \
  > evidence/glba-http-non-redirect-$(date +%Y%m%d).json

# CloudFront TLS versions (must be TLS 1.2+)
aws cloudfront list-distributions \
  --query 'DistributionList.Items[].[Id,ViewerCertificate.MinimumProtocolVersion]' \
  --output json > evidence/glba-cloudfront-tls-$(date +%Y%m%d).json

Collection Frequency: Monthly Retention: 5 years Purpose: Demonstrates encryption in transit per §314.4(c)(4)

✓ Multi-Factor Authentication Evidence (§314.4(c)(6))

# IAM Credential Report - MFA status
aws iam generate-credential-report
aws iam get-credential-report --output text | base64 -d \
  > evidence/glba-iam-credential-report-$(date +%Y%m%d).csv

# Users without MFA (non-compliant)
aws iam get-credential-report --output text | base64 -d | \
  awk -F',' '$4 == "true" && $8 == "false" {print $1}' \
  > evidence/glba-no-mfa-$(date +%Y%m%d).txt

# Count MFA compliance
total_users=$(aws iam get-credential-report --output text | base64 -d | tail -n +2 | wc -l)
mfa_users=$(aws iam get-credential-report --output text | base64 -d | awk -F',' '$8 == "true"' | wc -l)
echo "MFA Compliance: $mfa_users / $total_users users" > evidence/glba-mfa-summary-$(date +%Y%m%d).txt

Collection Frequency: Weekly Retention: 5 years Purpose: MFA requirement per §314.4(c)(6)

✓ Access Controls Evidence (§314.4(c)(1-2))

# IAM policies - least privilege review
aws iam list-policies --scope Local --output json \
  > evidence/glba-iam-policies-$(date +%Y%m%d).json

# Users with AdministratorAccess (should be minimal)
for user in $(aws iam list-users --query 'Users[].UserName' --output text); do
  policies=$(aws iam list-attached-user-policies --user-name "$user" --query 'AttachedPolicies[?PolicyName==`AdministratorAccess`]')
  if [ "$policies" != "[]" ]; then
    echo "$user has AdministratorAccess" >> evidence/glba-admin-users-$(date +%Y%m%d).txt
  fi
done

# Security groups allowing 0.0.0.0/0 access (potential risk)
aws ec2 describe-security-groups \
  --filters "Name=ip-permission.cidr,Values=0.0.0.0/0" \
  --query 'SecurityGroups[].[GroupId,GroupName,IpPermissions[?IpRanges[?CidrIp==`0.0.0.0/0`]]]' \
  --output json > evidence/glba-open-security-groups-$(date +%Y%m%d).json

Collection Frequency: Monthly Retention: 5 years Purpose: Access controls per §314.4(c)(1-2)

✓ Vulnerability Assessment Evidence (§314.4(d)(2))

# AWS Inspector findings
aws inspector2 list-findings \
  --filter-criteria '{"severity":[{"comparison":"EQUALS","value":"CRITICAL"},{"comparison":"EQUALS","value":"HIGH"}]}' \
  --max-results 1000 \
  --output json > evidence/glba-inspector-findings-$(date +%Y%m%d).json

# Security Hub findings
aws securityhub get-findings \
  --filters '{"SeverityLabel":[{"Value":"CRITICAL","Comparison":"EQUALS"},{"Value":"HIGH","Comparison":"EQUALS"}],"RecordState":[{"Value":"ACTIVE","Comparison":"EQUALS"}]}' \
  --max-results 100 \
  --output json > evidence/glba-securityhub-findings-$(date +%Y%m%d).json

# Summarize vulnerability count
critical_count=$(aws inspector2 list-findings --filter-criteria '{"severity":[{"comparison":"EQUALS","value":"CRITICAL"}]}' --query 'findings | length(@)')
high_count=$(aws inspector2 list-findings --filter-criteria '{"severity":[{"comparison":"EQUALS","value":"HIGH"}]}' --query 'findings | length(@)')
echo "Critical: $critical_count, High: $high_count" > evidence/glba-vulnerability-summary-$(date +%Y%m%d).txt

Collection Frequency: Weekly Retention: 5 years Purpose: Vulnerability assessments per §314.4(d)(2)

✓ Monitoring Evidence (§314.4(d)(1))

# CloudWatch alarms configured (continuous monitoring)
aws cloudwatch describe-alarms --output json \
  > evidence/glba-cloudwatch-alarms-$(date +%Y%m%d).json

# GuardDuty findings (threat detection)
aws guardduty list-findings \
  --detector-id $(aws guardduty list-detectors --query 'DetectorIds[0]' --output text) \
  --finding-criteria '{"Criterion":{"severity":{"Gte":7}}}' \
  --output json > evidence/glba-guardduty-findings-$(date +%Y%m%d).json

# CloudTrail enabled (audit logging)
aws cloudtrail describe-trails --output json \
  > evidence/glba-cloudtrail-status-$(date +%Y%m%d).json

Collection Frequency: Monthly summary Retention: 5 years Purpose: Continuous monitoring per §314.4(d)(1)

✓ Secure Disposal Evidence (§314.4(c)(7))

# S3 lifecycle policies (automated deletion)
aws s3api list-buckets --output json | jq -r '.Buckets[].Name' | while read bucket; do
  lifecycle=$(aws s3api get-bucket-lifecycle-configuration --bucket "$bucket" 2>&1)
  if echo "$lifecycle" | grep -q "NoSuchLifecycleConfiguration"; then
    echo "$bucket,NO LIFECYCLE POLICY" >> evidence/glba-lifecycle-policies-$(date +%Y%m%d).csv
  else
    echo "$bucket,HAS LIFECYCLE POLICY" >> evidence/glba-lifecycle-policies-$(date +%Y%m%d).csv
  fi
done

Collection Frequency: Quarterly Retention: 5 years Purpose: Disposal procedures per §314.4(c)(7)

Manual Evidence Collection

□ Annual Risk Assessment

  • Comprehensive risk assessment performed annually (minimum)
  • Required elements per §314.4(b):
    • Identify reasonably foreseeable internal and external threats
    • Assess likelihood and potential damage of threats
    • Assess sufficiency of current safeguards
    • Identify gaps and prioritize remediation
  • Evidence: Annual Risk Assessment Report (signed by Qualified Individual, reviewed by Board)
  • Frequency: Annually minimum

□ Annual Penetration Test (§314.4(d)(3))

  • Full penetration test of systems storing/processing customer information
  • Scope: External and internal tests
  • Required elements:
    • Test methodology and scope
    • Findings (vulnerabilities, exploits successful)
    • Risk ratings (critical, high, medium, low)
    • Remediation recommendations
    • Retest results (for critical/high findings)
  • Evidence: Penetration test report + remediation tracker
  • Frequency: Annually minimum

□ Security Awareness Training Records

  • All personnel complete annual security training
  • Topics: Safeguards Rule requirements, customer information handling, phishing awareness, incident reporting
  • Evidence: Training completion records (100% of employees), training materials, quiz scores
  • Frequency: Annually, on hire for new employees

□ Service Provider Due Diligence (§314.4(f))

  • Due diligence before selecting service provider
  • Required elements:
    • Service provider security posture assessment
    • SOC 2 Type II report review (if available)
    • Questionnaire responses
    • Contract review (security requirements)
    • Ongoing monitoring plan
  • Evidence: Due diligence reports (one per service provider), contracts with security clauses
  • Frequency: Before engagement, annual review

□ Service Provider Contracts

  • Written contracts with all service providers (§314.4(f)(2))
  • Required clauses:
    • Implement and maintain appropriate safeguards
    • Protect confidentiality and security of customer information
    • Restrict use of customer information to purposes specified
    • Disposal requirements
    • Incident notification (prompt notification to institution)
  • Evidence: Signed contracts with security clauses
  • Frequency: Before engagement, review every 2-3 years

□ Annual Board Report (§314.4(i))

  • Written report to Board of Directors (or equivalent governing body)
  • Required content:
    • Overall status of information security program
    • Compliance with Safeguards Rule requirements
    • Material matters (risk assessment results, incidents, service provider issues, testing results)
    • Recommended changes or improvements
  • Evidence: Annual Board Report + Board meeting minutes acknowledging report
  • Frequency: Annually

□ Incident Log

  • Log of all security incidents (breaches, near-misses)
  • Required elements:
    • Date/time of incident
    • Type of incident
    • Systems/data affected
    • Root cause analysis
    • Containment and remediation actions
    • Lessons learned
    • Notification to customers (if applicable per state law)
  • Evidence: Incident register + investigation reports
  • Frequency: Ongoing

Safeguards Rule Compliance Assessment

Regulators (FTC, FDIC, OCC, NCUA) will verify:

Documentation Review

✓ Written Information Security Program (WISP) exists and is comprehensive ✓ Qualified Individual designated in writing ✓ Annual risk assessments performed (documented) ✓ Safeguards documented for all identified risks ✓ Monitoring and testing program documented ✓ Training program documented ✓ Service provider oversight documented ✓ Incident response plan documented ✓ Annual Board reports submitted and reviewed

Implementation Review

✓ Encryption at rest for customer information ✓ Encryption in transit (TLS 1.2+ for all customer data transmission) ✓ MFA implemented for accessing customer information ✓ Access controls (least privilege, user authentication) ✓ Secure disposal procedures ✓ Change management process ✓ Service provider contracts include required security clauses

Testing and Validation

✓ Annual penetration testing performed ✓ Vulnerability assessments performed (at least annually) ✓ Continuous monitoring or periodic testing in place ✓ Incident response plan tested ✓ Training completion records (100% of staff)

Common Regulatory Findings

Critical (Likely to Result in Enforcement Action)

❌ No Written Information Security Program (WISP) ❌ No Qualified Individual designated ❌ No annual risk assessment performed ❌ No encryption of customer information at rest or in transit ❌ No multi-factor authentication for accessing customer information ❌ No annual penetration testing ❌ No annual Board report

Moderate (Requires Remediation)

⚠️ WISP incomplete (missing required elements) ⚠️ Risk assessment not performed annually ⚠️ Some customer information not encrypted ⚠️ MFA not enforced for all access to customer information ⚠️ Service provider contracts missing required security clauses ⚠️ Penetration test >12 months old ⚠️ Incident response plan not tested

Minor (Best Practice Recommendations)

⚠️ WISP not reviewed in last 12 months ⚠️ Training completion not 100% ⚠️ Service provider assessments not performed annually ⚠️ Monitoring dashboards incomplete

Remediation Guidance

If No WISP Exists

  1. Week 1: Download FTC WISP template and customize
  2. Weeks 2-4: Document all required elements (risk assessment process, safeguards, monitoring, training, service providers, incident response)
  3. Week 5: Review with Qualified Individual and legal counsel
  4. Week 6: Present to Board for approval
  5. Week 7: Distribute to organization and begin implementation

Timeline: 6-8 weeks Priority: 🔴 CRITICAL (foundational requirement)

If No MFA Implemented

  1. Week 1: Inventory all systems accessing customer information
  2. Week 2: Select MFA solution (AWS IAM MFA, Okta, Duo, etc.)
  3. Weeks 3-4: Pilot MFA with IT team
  4. Weeks 5-8: Roll out to all users accessing customer information
  5. Week 9: Enforce MFA (no access without MFA)

Timeline: 8-10 weeks Priority: 🔴 CRITICAL (§314.4(c)(6) requirement)

If No Annual Penetration Test

  1. Week 1: Select penetration testing vendor
  2. Week 2: Define scope (external + internal tests, systems with customer information)
  3. Weeks 3-6: Execute penetration test
  4. Week 7: Receive report and findings
  5. Weeks 8-12: Remediate critical and high findings
  6. Week 13: Retest critical/high findings

Timeline: 12-14 weeks Priority: 🔴 CRITICAL (§314.4(d)(3) requirement)

Cross-References

Related GLBA Rules

  • Privacy Rule (16 CFR Part 313) - Privacy notices to customers
  • Pretexting Rule (16 CFR Part 517) - Protection against pretexting

Maps to Other Frameworks

  • NIST 800-53: All families (GLBA aligns closely with NIST)
  • NIST Cybersecurity Framework: All 5 functions
  • ISO 27001:2022: Annex A controls
  • SOC 2: All Trust Service Criteria
  • FFIEC Cybersecurity Assessment Tool: All domains

Cost Estimates

GLBA Safeguards Rule Compliance (Small Financial Institution)

  • WISP development: 80 hours ($8,000)
  • Annual risk assessment: 60 hours ($6,000/year)
  • Penetration testing: $15k-$30k/year
  • Vulnerability scanning: $5k-$10k/year
  • MFA implementation: 40 hours + $5k software ($9,000 one-time, $2k/year ongoing)
  • Security awareness training: 16 hours development + 2 hours per employee ($2,000 + $100/person)
  • Service provider due diligence: 40 hours ($4,000/year)
  • Incident response plan: 40 hours ($4,000)
  • Total Year 1: ~$48k-$63k (one-time) + $28k-$38k (ongoing)
  • Ongoing: ~$28k-$38k/year

Qualified Individual

  • Dedicated CISO (if hired): $120k-$200k/year + benefits
  • Virtual CISO (outsourced): $5k-$15k/month ($60k-$180k/year)
  • Existing IT Director (additional responsibilities): +$10k-$30k/year

Tools

  • GRC platform: $15k-$50k/year
  • SIEM: $20k-$100k/year
  • Vulnerability management: $5k-$15k/year
  • MFA solution: $3-10/user/month

Evidence Package Structure

evidence/
└── glba-safeguards-rule/
    ├── wisp/
    │   ├── wisp-v1.2-board-approved.pdf
    │   ├── qualified-individual-designation.pdf
    │   └── board-approval-minutes-2024-01-15.pdf
    ├── risk-assessments/
    │   ├── risk-assessment-2024.pdf
    │   ├── risk-assessment-2023.pdf
    │   └── risk-register-master.xlsx
    ├── safeguards/
    │   ├── encryption-at-rest-policy.pdf
    │   ├── encryption-in-transit-policy.pdf
    │   ├── mfa-policy.pdf
    │   ├── access-control-policy.pdf
    │   └── evidence/ (automated monthly evidence)
    ├── monitoring-testing/
    │   ├── penetration-test-2024.pdf
    │   ├── vulnerability-scans/ (monthly)
    │   ├── monitoring-dashboards-screenshots.pdf
    │   └── remediation-tracker.xlsx
    ├── training/
    │   ├── training-materials-2024.pdf
    │   ├── completion-records-2024.xlsx
    │   └── attendance-registers/
    ├── service-providers/
    │   ├── service-provider-inventory.xlsx
    │   ├── due-diligence-reports/
    │   ├── contracts/
    │   └── annual-assessments/
    ├── incident-response/
    │   ├── incident-response-plan-v1.1.pdf
    │   ├── incident-log-master.xlsx
    │   └── incident-investigations/
    ├── board-reports/
    │   ├── annual-board-report-2024.pdf
    │   ├── board-minutes-2024-12-15.pdf
    │   └── ... (annual reports + minutes)
    └── README.md (evidence index, 5-year retention)

Automation Script

#!/usr/bin/env python3
"""
GLBA Safeguards Rule Evidence Collection
For financial institutions subject to FTC Safeguards Rule
"""
import boto3
import json
import csv
from datetime import datetime
import os

class GLBASafeguardsEvidence:
    def __init__(self, output_dir="evidence/glba-safeguards-rule"):
        self.output_dir = output_dir
        self.timestamp = datetime.now().strftime("%Y%m%d")
        os.makedirs(f"{output_dir}/safeguards/evidence", exist_ok=True)

    def check_encryption_at_rest(self):
        """Check encryption at rest (§314.4(c)(3))"""
        print("Checking encryption at rest compliance...")
        s3 = boto3.client('s3')
        rds = boto3.client('rds')

        # S3 encryption
        buckets = s3.list_buckets()['Buckets']
        s3_results = []
        for bucket in buckets:
            bucket_name = bucket['Name']
            try:
                encryption = s3.get_bucket_encryption(Bucket=bucket_name)
                s3_results.append({'bucket': bucket_name, 'encrypted': True})
            except:
                s3_results.append({'bucket': bucket_name, 'encrypted': False})

        # RDS encryption
        rds_instances = rds.describe_db_instances()['DBInstances']
        rds_results = []
        for instance in rds_instances:
            rds_results.append({
                'instance': instance['DBInstanceIdentifier'],
                'encrypted': instance.get('StorageEncrypted', False)
            })

        # Save evidence
        with open(f"{self.output_dir}/safeguards/evidence/s3-encryption-{self.timestamp}.json", 'w') as f:
            json.dump(s3_results, f, indent=2)

        with open(f"{self.output_dir}/safeguards/evidence/rds-encryption-{self.timestamp}.json", 'w') as f:
            json.dump(rds_results, f, indent=2)

        s3_encrypted = len([r for r in s3_results if r['encrypted']])
        rds_encrypted = len([r for r in rds_results if r['encrypted']])

        print(f"✓ S3 buckets: {s3_encrypted}/{len(s3_results)} encrypted")
        print(f"✓ RDS instances: {rds_encrypted}/{len(rds_instances)} encrypted")

        return {'s3': s3_results, 'rds': rds_results}

    def check_mfa_compliance(self):
        """Check MFA enforcement (§314.4(c)(6))"""
        print("Checking MFA compliance...")
        iam = boto3.client('iam')

        # Generate credential report
        iam.generate_credential_report()
        report = iam.get_credential_report()

        # Parse for MFA status
        users_without_mfa = []
        total_users = 0

        for line in csv.DictReader(report['Content'].decode('utf-8').splitlines()):
            if line.get('password_enabled') == 'true':
                total_users += 1
                if line.get('mfa_active') == 'false':
                    users_without_mfa.append({
                        'user': line['user'],
                        'password_last_used': line.get('password_last_used')
                    })

        # Save evidence
        with open(f"{self.output_dir}/safeguards/evidence/mfa-compliance-{self.timestamp}.json", 'w') as f:
            json.dump({
                'total_users': total_users,
                'mfa_enabled': total_users - len(users_without_mfa),
                'mfa_disabled': len(users_without_mfa),
                'compliance_percentage': (total_users - len(users_without_mfa)) / total_users * 100 if total_users > 0 else 0,
                'users_without_mfa': users_without_mfa
            }, f, indent=2)

        print(f"✓ MFA compliance: {total_users - len(users_without_mfa)}/{total_users} users ({(total_users - len(users_without_mfa)) / total_users * 100:.1f}%)")

        if len(users_without_mfa) > 0:
            print(f"⚠️  WARNING: {len(users_without_mfa)} users without MFA (§314.4(c)(6) non-compliant)")

        return users_without_mfa

    def check_vulnerability_findings(self):
        """Check vulnerability assessment results (§314.4(d)(2))"""
        print("Checking vulnerability assessment compliance...")
        inspector = boto3.client('inspector2')

        # Get critical and high findings
        findings = inspector.list_findings(
            filterCriteria={
                'severity': [
                    {'comparison': 'EQUALS', 'value': 'CRITICAL'},
                    {'comparison': 'EQUALS', 'value': 'HIGH'}
                ]
            },
            maxResults=1000
        )

        # Save evidence
        with open(f"{self.output_dir}/safeguards/evidence/vulnerability-findings-{self.timestamp}.json", 'w') as f:
            json.dump(findings, f, indent=2, default=str)

        finding_count = len(findings.get('findings', []))
        print(f"✓ Critical/High vulnerabilities: {finding_count}")

        if finding_count > 0:
            print(f"⚠️  ACTION REQUIRED: Remediate {finding_count} critical/high vulnerabilities")

        return finding_count

    def generate_compliance_report(self, encryption_results, mfa_results, vuln_count):
        """Generate GLBA Safeguards Rule compliance summary"""
        s3_compliant = all(r['encrypted'] for r in encryption_results['s3'])
        rds_compliant = all(r['encrypted'] for r in encryption_results['rds'])
        mfa_compliant = len(mfa_results) == 0

        report = f"""
GLBA Safeguards Rule Compliance Report
Generated: {datetime.now().strftime("%Y-%m-%d %H:%M:%S")}
Regulation: 16 CFR Part 314

ENCRYPTION AT REST (§314.4(c)(3))
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
S3 Buckets:       {len([r for r in encryption_results['s3'] if r['encrypted']])}/{len(encryption_results['s3'])} encrypted {'✓ COMPLIANT' if s3_compliant else '✗ NON-COMPLIANT'}
RDS Databases:    {len([r for r in encryption_results['rds'] if r['encrypted']])}/{len(encryption_results['rds'])} encrypted {'✓ COMPLIANT' if rds_compliant else '✗ NON-COMPLIANT'}

MULTI-FACTOR AUTHENTICATION (§314.4(c)(6))
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
MFA Compliance:   {'✓ COMPLIANT - All users have MFA' if mfa_compliant else f'✗ NON-COMPLIANT - {len(mfa_results)} users without MFA'}

VULNERABILITY ASSESSMENTS (§314.4(d)(2))
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Critical/High:    {vuln_count} findings {'⚠️  Remediation required' if vuln_count > 0 else '✓ No critical/high findings'}

OVERALL COMPLIANCE STATUS
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
{'✓ COMPLIANT' if s3_compliant and rds_compliant and mfa_compliant and vuln_count == 0 else '✗ NON-COMPLIANT - Remediation Required'}

REQUIRED ACTIONS
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
"""
        if not s3_compliant:
            report += "□ Enable S3 encryption for all buckets with customer information\n"
        if not rds_compliant:
            report += "□ Enable RDS encryption for all databases with customer information\n"
        if not mfa_compliant:
            report += f"□ Enable MFA for {len(mfa_results)} IAM users\n"
        if vuln_count > 0:
            report += f"□ Remediate {vuln_count} critical/high vulnerabilities\n"

        report += """
ANNUAL REQUIREMENTS REMINDER
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
□ Annual risk assessment (§314.4(b))
□ Annual penetration test (§314.4(d)(3))
□ Annual vulnerability assessment (§314.4(d)(2))
□ Annual Board report (§314.4(i))
□ Annual security awareness training (§314.4(e))

Evidence Location: {self.output_dir}/safeguards/evidence/
Retention: 5 years (financial services standard)
"""

        report_file = f"{self.output_dir}/compliance-report-{self.timestamp}.txt"
        with open(report_file, 'w') as f:
            f.write(report)

        print(f"\n{report}")
        return report_file

if __name__ == "__main__":
    print("GLBA Safeguards Rule Evidence Collection")
    print("=" * 70)
    print("Regulation: 16 CFR Part 314 (Amended December 9, 2022)")
    print("=" * 70)

    collector = GLBASafeguardsEvidence()

    encryption_results = collector.check_encryption_at_rest()
    mfa_results = collector.check_mfa_compliance()
    vuln_count = collector.check_vulnerability_findings()

    collector.generate_compliance_report(encryption_results, mfa_results, vuln_count)

    print("\n✓ GLBA evidence collection complete")
    print("⚠️  REMINDER: Annual penetration test and Board report required")

GLBA Regulation: 16 CFR Part 314 (Safeguards Rule) Regulator: FTC, FDIC, OCC, NCUA, SEC (depending on institution type) Effective Date: December 9, 2022 (amended rule) Penalties: Up to $46,517 per violation per day Evidence Retention: 5 years (financial services standard) Priority: 🔴 CRITICAL (US financial institutions)

GLBA Privacy Rule Compliance

Provides guidance on implementing the GLBA Privacy Rule (16 CFR Part 313) requirements for consumer privacy notices and information sharing.

Arguments

  • $1 - Focus area (required: all, initial-notice, annual-notice, opt-out, sharing-practices, exceptions)
  • $2 - Delivery method (optional: paper, electronic, website)

Privacy Rule Overview

Authority: 16 CFR Part 313 Effective: July 1, 2001 (with amendments) Purpose: Ensure consumers receive clear privacy notices and control over information sharing Enforced by: FTC, banking regulators, SEC, state regulators

Core Requirements

1. Initial Privacy Notice

Requirement: Provide clear, conspicuous privacy notice before establishing customer relationship

Timing:

  • At account opening
  • Before disclosing nonpublic personal information
  • Not later than when relationship established

Content Requirements:

  1. Information Collection:

    • Categories of nonpublic personal information collected
    • Sources of information (customer, transactions, third parties)
  2. Information Sharing:

    • Categories shared with affiliates
    • Categories shared with nonaffiliated third parties
    • Purpose of sharing
  3. Security Practices:

    • Policies and practices to protect information
    • Safeguards implemented
  4. Consumer Rights:

    • Right to opt-out of certain sharing
    • How to exercise opt-out rights
  5. Contact Information:

    • How to contact institution
    • Customer service contact details

Format Requirements:

  • Clear and conspicuous
  • Reasonably understandable
  • Plain language
  • Separate document or prominent part of document

2. Annual Privacy Notice

Requirement: Provide annual privacy notice to customers at least once in 12-month period

Exception: Annual notice NOT required if:

  1. Only share with affiliates
  2. Only share under GLBA exceptions (service providers, joint marketing)
  3. Have not changed privacy policies

Many institutions now exempt from annual notice requirement due to 2015 FAST Act amendments

When Required:

  • Share with nonaffiliated third parties beyond exceptions
  • Privacy policies have changed

Delivery Timing:

  • At least once in any 12-month period
  • No requirement to coordinate with account anniversary

3. Revised Privacy Notice

Requirement: Provide revised notice before implementing material changes to privacy policies

Material Changes:

  • New categories of information collected
  • New categories of affiliates/third parties to whom info disclosed
  • New purposes for disclosure
  • Changes to opt-out rights
  • Changes to security policies

Timing: Reasonable time before implementing change

Opt-Out: New opt-out right required if change affects previous opt-out

4. Opt-Out Rights

Requirement: Allow consumers to opt-out of information sharing with nonaffiliated third parties

When Opt-Out Required:

  • Sharing nonpublic personal information with nonaffiliated third parties
  • Sharing beyond GLBA exceptions

When Opt-Out NOT Required (Exceptions):

  • Sharing with service providers (processing transactions)
  • Joint marketing agreements (with customer authorization)
  • Sharing as permitted by law
  • Sharing with consumer reporting agencies
  • Sharing necessary to effect transaction customer requested

Opt-Out Mechanisms:

  • Must provide reasonable means to opt-out
  • Examples: Check-off box, reply form, toll-free number, online portal
  • Must allow opt-out at any time
  • Opt-out effective within reasonable time (30 days standard)

Opt-Out Duration:

  • Continues until revoked by consumer
  • Revocation must be voluntary and clear
  • Institution may require periodic reaffirmation (but not mandatory)

Information Categories

Nonpublic Personal Information (NPI)

Definition: Personally identifiable financial information not publicly available

Examples:

  • Name, address, SSN, income
  • Account numbers and balances
  • Transaction history
  • Credit scores and reports
  • Information from applications
  • Information from consumer reports

NOT NPI:

  • Publicly available information (phone book, government records)
  • De-identified/aggregated data
  • Information customer authorizes to be public

Affiliate vs. Nonaffiliated Third Party

Affiliate:

  • Company controlled by, controlling, or under common control
  • Example: Parent company, subsidiaries, sister companies
  • Rule: Can share with affiliates without opt-out (but annual notice may be required under FCRA)

Nonaffiliated Third Party:

  • Any entity not affiliated
  • Examples: Marketing companies, data brokers, unrelated financial institutions
  • Rule: Must provide opt-out unless exception applies

Privacy Notice Delivery Methods

Paper Delivery

Methods:

  • Mailed to customer's address
  • Hand-delivered at branch/office
  • Included with account statements

Advantages:

  • Accessible to all customers
  • Creates physical record
  • Familiar to customers

Disadvantages:

  • Printing and mailing costs
  • Delivery delays
  • Environmental impact

Electronic Delivery

Methods:

  • Email (with PDF attachment or link)
  • Website posting (with customer acknowledgment)
  • Mobile app notification
  • Secure messaging portal

E-SIGN Act Requirements:

  1. Consumer Consent: Affirmative consent to electronic delivery
  2. Demonstration of Access: Consumer demonstrates ability to access electronic records
  3. Hardware/Software Requirements: Disclose technical requirements
  4. Right to Paper: Consumer can request paper copy
  5. Change Notice: Notify if hardware/software requirements change

Advantages:

  • Cost-effective
  • Immediate delivery
  • Eco-friendly
  • Easy to update

Disadvantages:

  • Requires customer consent
  • Technology barriers
  • Spam filters may block
  • Accessibility concerns

Website Posting

Continuous Access Method: Post privacy notice on public website

Requirements:

  • Prominently placed
  • Clearly labeled ("Privacy Policy" or "Privacy Notice")
  • Easily accessible (typically footer link)
  • Available without login

Note: Website posting alone does NOT satisfy delivery requirement; must also provide notice to customer directly

Sharing Practices

Permissible Sharing (No Opt-Out Required)

1. Service Providers and Joint Marketing:

  • Sharing with service providers to perform services for institution
  • Examples: Data processors, statement printers, payment processors
  • Contract Required: Service provider must maintain confidentiality

Joint Marketing: Marketing by institution and nonaffiliated financial institution together

  • Agreement Required: Formal joint marketing agreement

2. Exceptions Under Section 313.14/313.15:

  • Sharing to process transactions customer requested
  • Sharing to maintain or service account
  • Sharing to resolve disputes or inquiries
  • Sharing to comply with laws, regulations, legal process
  • Sharing to prevent fraud
  • Sharing with consumer reporting agencies
  • Sharing in connection with sale or merger

Restricted Sharing (Opt-Out Required)

Examples:

  • Selling customer lists to marketers
  • Sharing for third-party marketing purposes
  • Providing information to data brokers
  • Cross-selling arrangements with nonaffiliates

Opt-Out Requirement: Must provide clear opt-out mechanism and honor consumer choices

Privacy Notice Templates

Model Privacy Form (Appendix A to Part 313)

FTC Provides: Optional model privacy form (safe harbor)

  • Use of model form deemed compliant
  • Specific format and content prescribed
  • Tables for information categories
  • Standard disclosures

Benefits:

  • Safe harbor compliance
  • Consistent consumer experience
  • Reduced legal risk

Customization: Institutions can modify but lose safe harbor if deviate significantly

Custom Privacy Notices

Requirements:

  • Must include all required content
  • Clear and conspicuous
  • Reasonably understandable
  • Accurate and not misleading

Best Practices:

  • Use plain language
  • Avoid legal jargon
  • Use tables/charts for clarity
  • Highlight key information
  • Provide examples
  • Make opt-out instructions prominent

State Privacy Laws

State Law Interaction

Preemption: GLBA preempts state laws only to extent they are inconsistent Greater Protection: States can require MORE privacy protection, not less

State-Specific Requirements:

  • California: CCPA/CPRA additional requirements
  • Vermont: Strict opt-in for data broker sharing
  • New York: NYDFS cybersecurity and privacy requirements

Multi-State Compliance: Institutions must comply with GLBA AND applicable state laws

Common Compliance Issues

  1. Outdated Privacy Notices:

    • Notice doesn't reflect current practices
    • New sharing practices not disclosed
    • Solution: Annual review and update of privacy notice
  2. Improper Delivery:

    • Electronic delivery without proper consent
    • Notice not provided at account opening
    • Solution: Implement delivery controls and verification
  3. Confusing Opt-Out Process:

    • Opt-out mechanism not clear
    • Website links broken
    • Phone numbers disconnected
    • Solution: Regular testing of opt-out mechanisms
  4. Inadequate Notice Content:

    • Missing required disclosures
    • Vague or misleading language
    • Solution: Use model form or legal review
  5. Failure to Honor Opt-Out:

    • Continuing to share after opt-out
    • System errors
    • Solution: Opt-out tracking system, compliance audits
  6. Service Provider Oversight:

    • No confidentiality contracts
    • Inadequate vendor monitoring
    • Solution: Standardized service provider agreements with privacy clauses

FTC Enforcement Examples

Recent Actions:

  • Credit Karma (2022): $3M penalty for deceptive pre-approved claims and privacy violations
  • CafePress (2021): Data breach, inadequate security, misleading privacy claims
  • PayPal (2018): Venmo privacy settings misleading
  • TaxSlayer (2017): Data breach, inadequate security despite privacy promises

Common Violations:

  • Misleading privacy statements
  • Failure to implement stated privacy practices
  • Inadequate security despite privacy promises
  • Deceptive opt-out processes

Privacy and Security Intersection

Privacy Rule + Safeguards Rule:

  • Privacy Rule: What you SAY about information practices
  • Safeguards Rule: What you DO to protect information
  • Consistency Required: Privacy statements must match actual security practices

Example Violations:

  • Privacy notice says "we encrypt your data" but encryption not implemented
  • Privacy notice says "we limit access" but no access controls in place
  • Consequence: FTC deception charges + Safeguards Rule violations

Examples

# Complete Privacy Rule compliance guidance
/glba:privacy all

# Initial privacy notice requirements
/glba:privacy initial-notice

# Annual privacy notice determination
/glba:privacy annual-notice electronic

# Opt-out mechanism implementation
/glba:privacy opt-out

# Information sharing practices review
/glba:privacy sharing-practices

# Exceptions to opt-out requirements
/glba:privacy exceptions

Checklist for Compliance

  • Initial privacy notice provided at account opening
  • Privacy notice includes all required content elements
  • Annual notice provided (if required based on sharing practices)
  • Opt-out mechanism available and functional
  • Opt-out requests tracked and honored
  • Service provider contracts include confidentiality requirements
  • Privacy notice reviewed and updated annually
  • Electronic delivery has proper E-SIGN consent
  • Website privacy policy is current and accessible
  • Privacy practices match Safeguards Rule implementation
  • State-specific privacy requirements addressed
  • Staff trained on privacy requirements
  • Privacy compliance audited periodically

GLBA Risk Assessment

Provides methodology and guidance for conducting risk assessments required under the GLBA Safeguards Rule.

Arguments

  • $1 - Assessment phase (required: planning, execution, reporting, all)
  • $2 - Methodology (optional: nist, iso, qualitative, quantitative)

Risk Assessment Requirement

Authority: 16 CFR Part 314.4(b) - Safeguards Rule Element #2 Requirement: "Identify and assess reasonably foreseeable internal and external risks to the security, confidentiality, and integrity of customer information"

Purpose:

  • Understand threats and vulnerabilities
  • Prioritize security investments
  • Demonstrate due diligence
  • Support board reporting
  • Guide safeguard selection

Frequency:

  • At least annually
  • When significant changes occur
  • After security incidents
  • When new systems/processes introduced

Risk Assessment Phases

Phase 1: Planning

Objectives:

  • Define scope and boundaries
  • Select methodology
  • Assemble team
  • Schedule activities
  • Gather preliminary information

Scope Definition:

  1. Information Assets:

    • Customer information (NPI)
    • Systems storing/processing NPI
    • Databases and data repositories
    • Backup systems
    • Cloud services
  2. Physical Locations:

    • Branch offices
    • Data centers
    • Remote work environments
    • Third-party facilities
  3. Processes:

    • Account opening
    • Transaction processing
    • Customer service
    • Marketing
    • IT operations
  4. People:

    • Employees with access to customer data
    • Contractors and vendors
    • Service providers

Team Composition:

  • Risk assessment lead
  • IT/security personnel
  • Business unit representatives
  • Compliance officer
  • Legal counsel (as needed)
  • External consultants (if applicable)

Phase 2: Execution

Step 1: Asset Identification

Information Assets:

  • Customer databases
  • Transaction systems
  • CRM systems
  • Document management
  • Email archives
  • Backup tapes/systems

Inventory Details:

  • Asset name/description
  • Data classification (customer information, sensitive, public)
  • Storage location (on-premise, cloud, hybrid)
  • Access controls
  • Retention period

Step 2: Threat Identification

External Threats:

  1. Cyberattacks:

    • Ransomware
    • Phishing/social engineering
    • DDoS attacks
    • SQL injection
    • Zero-day exploits
    • Advanced persistent threats (APT)
  2. Environmental:

    • Natural disasters (flood, fire, earthquake)
    • Power outages
    • HVAC failures
  3. Third-Party:

    • Cloud provider outages
    • Vendor data breaches
    • Supply chain attacks

Internal Threats:

  1. Insider Threats:

    • Malicious employees
    • Negligent employees
    • Compromised credentials
    • Privilege abuse
  2. Operational:

    • Human error
    • Process failures
    • System misconfigurations
    • Change management failures
  3. Technology:

    • Aging infrastructure
    • Unpatched vulnerabilities
    • Insufficient capacity
    • Single points of failure

Step 3: Vulnerability Analysis

Technical Vulnerabilities:

  • Missing patches
  • Weak authentication
  • Unencrypted data
  • Open network shares
  • Default configurations
  • Legacy systems
  • Insufficient logging

Administrative Vulnerabilities:

  • Inadequate policies
  • Lack of security awareness
  • Unclear roles/responsibilities
  • Insufficient vendor oversight
  • No incident response plan

Physical Vulnerabilities:

  • Inadequate access controls
  • No visitor management
  • Unsecured disposal
  • Environmental controls lacking

Assessment Methods:

  • Vulnerability scanning (automated tools)
  • Configuration reviews
  • Policy/procedure reviews
  • Penetration testing
  • Physical security assessments
  • Interviews with staff

Step 4: Likelihood Assessment

Factors to Consider:

  • Threat actor capability
  • Threat actor motivation
  • Ease of exploitation
  • Existing controls
  • Historical incidents
  • Industry trends

Likelihood Ratings:

  • Low: Unlikely to occur (0-25% probability)
  • Medium: May occur (25-75% probability)
  • High: Likely to occur (75-100% probability)

Evidence Sources:

  • Threat intelligence feeds
  • Industry reports (Verizon DBIR, etc.)
  • Incident history
  • Security assessments
  • Vulnerability scan results

Step 5: Impact Analysis

Impact Categories:

  1. Financial Impact:

    • Direct losses (fraud, theft)
    • Regulatory fines and penalties
    • Legal costs
    • Remediation costs
    • Customer compensation
    • Lost revenue
  2. Operational Impact:

    • Business disruption
    • System downtime
    • Recovery time
    • Customer service degradation
  3. Reputational Impact:

    • Customer trust erosion
    • Media coverage
    • Brand damage
    • Competitive disadvantage
  4. Compliance Impact:

    • Regulatory violations
    • Contractual breaches
    • Certification loss
    • Consent orders

Impact Ratings:

  • Low: Minimal impact, easily recoverable (<$50K, <1 day disruption)
  • Medium: Moderate impact, recoverable ($50K-$500K, 1-7 days disruption)
  • High: Severe impact, difficult recovery (>$500K, >7 days disruption, regulatory action)

Step 6: Control Evaluation

Existing Controls Inventory:

Preventive Controls:

  • Firewalls, IDS/IPS
  • Multi-factor authentication
  • Encryption
  • Access controls
  • Security awareness training
  • Patch management
  • Antivirus/anti-malware

Detective Controls:

  • Log monitoring
  • SIEM
  • Vulnerability scanning
  • Intrusion detection
  • Audit reviews

Corrective Controls:

  • Incident response plan
  • Backup and recovery
  • Business continuity plan
  • Patch deployment

Control Effectiveness:

  • Effective: Control adequately mitigates risk
  • Partially Effective: Control provides some mitigation
  • Ineffective: Control does not mitigate risk

Step 7: Risk Calculation

Risk Formula: Risk = Likelihood × Impact

Risk Matrix:

Low ImpactMedium ImpactHigh Impact
High LikelihoodMediumHighCritical
Medium LikelihoodLowMediumHigh
Low LikelihoodLowLowMedium

Risk Levels:

  • Critical: Immediate action required
  • High: Address within 30 days
  • Medium: Address within 90 days
  • Low: Monitor, address as resources allow

Residual Risk: Risk remaining after existing controls applied

Phase 3: Reporting

Risk Assessment Report Components:

  1. Executive Summary:

    • Assessment scope and methodology
    • Key findings
    • Overall risk posture
    • Top risks
    • Recommendations
  2. Methodology:

    • Framework used (NIST, ISO, etc.)
    • Assessment activities
    • Data sources
    • Limitations
  3. Asset Inventory:

    • Systems and data in scope
    • Criticality ratings
    • Data classifications
  4. Threat and Vulnerability Analysis:

    • Identified threats
    • Discovered vulnerabilities
    • Threat landscape summary
  5. Risk Register:

    • Risk ID
    • Risk description
    • Threat + Vulnerability
    • Likelihood rating
    • Impact rating
    • Risk level
    • Existing controls
    • Residual risk
    • Treatment recommendation
  6. Risk Treatment Plan:

    • Mitigation strategies
    • Responsible parties
    • Target completion dates
    • Resource requirements
    • Priority rankings
  7. Metrics and Trends:

    • Risk level distribution
    • Year-over-year comparison
    • Control maturity
    • Vulnerability trends

Audience-Specific Reporting:

  • Board of Directors: Executive summary, top risks, financial impact, strategic recommendations
  • Management: Detailed findings, operational recommendations, resource needs
  • Technical Teams: Vulnerability details, remediation steps, technical controls

Risk Assessment Methodologies

NIST-Based Approach

Framework: NIST SP 800-30 "Guide for Conducting Risk Assessments"

Process:

  1. Prepare for assessment
  2. Conduct assessment (identify threats, vulnerabilities, likelihood, impact)
  3. Communicate results
  4. Maintain assessment (ongoing)

Advantages:

  • Well-documented
  • Widely recognized
  • Comprehensive
  • Free/public resource

Tools: NIST 800-30 templates, RMF tools

ISO 27005 Approach

Framework: ISO/IEC 27005 "Information Security Risk Management"

Process:

  1. Context establishment
  2. Risk identification
  3. Risk analysis
  4. Risk evaluation
  5. Risk treatment

Advantages:

  • International standard
  • Aligns with ISO 27001
  • Systematic approach

Considerations: Requires ISO 27005 standard (not free)

Qualitative Methodology

Approach: Use subjective ratings (High/Medium/Low) for likelihood and impact

Advantages:

  • Fast and simple
  • Low resource requirements
  • Understandable to non-technical stakeholders

Disadvantages:

  • Subjective assessments
  • Harder to prioritize
  • May lack precision

Best For: Small institutions, initial assessments, limited resources

Quantitative Methodology

Approach: Calculate numerical risk values based on financial impact

Formulas:

  • ALE (Annual Loss Expectancy) = ARO × SLE
  • ARO (Annualized Rate of Occurrence): Expected frequency per year
  • SLE (Single Loss Expectancy): Expected loss per incident

Advantages:

  • Objective, data-driven
  • Enables cost-benefit analysis
  • Supports budget justification

Disadvantages:

  • Requires extensive data
  • Time-consuming
  • Difficult to quantify reputational impact

Best For: Large institutions, mature risk programs, justifying major investments

Risk Treatment Options

1. Mitigate (Reduce)

Strategy: Implement controls to reduce likelihood or impact

Examples:

  • Deploy MFA to reduce account compromise risk
  • Implement encryption to reduce data exposure impact
  • Add SIEM to improve detection

When Appropriate: Cost of control < risk reduction benefit

2. Transfer (Share)

Strategy: Shift risk to third party

Examples:

  • Cyber insurance
  • Outsource to managed service provider
  • Cloud service provider shared responsibility

When Appropriate: Cost-effective transfer available, residual risk acceptable

3. Accept (Retain)

Strategy: Acknowledge risk and take no additional action

Examples:

  • Low-likelihood, low-impact risks
  • Cost of mitigation exceeds potential loss
  • Business justification for accepting risk

Requirements:

  • Documented risk acceptance by management
  • Periodic review
  • Monitoring for changes

4. Avoid (Eliminate)

Strategy: Eliminate the risk by discontinuing activity

Examples:

  • Decommission vulnerable legacy system
  • Discontinue high-risk service
  • Exit high-risk market

When Appropriate: Risk unacceptable and cannot be adequately mitigated

Common Risk Assessment Challenges

  1. Scope Creep:

    • Assessment expands beyond original scope
    • Solution: Clear boundaries, phased approach
  2. Data Availability:

    • Incomplete asset inventory
    • Lack of historical incident data
    • Solution: Discovery tools, industry benchmarks, assumptions
  3. Subjectivity:

    • Inconsistent likelihood/impact ratings
    • Solution: Defined rating criteria, calibration sessions
  4. Resource Constraints:

    • Limited staff time
    • Budget limitations
    • Solution: Prioritized scope, automated tools, consultants
  5. Stakeholder Engagement:

    • Business units unresponsive
    • Lack of executive support
    • Solution: Executive sponsorship, communicate value, involve early

Integration with Safeguards Rule

Risk Assessment Feeds:

  1. Safeguard Selection (Element #3): Use risk assessment to prioritize controls
  2. Monitoring and Testing (Element #4): Focus testing on high-risk areas
  3. Training (Element #5): Tailor training to identified threats
  4. Service Provider Selection (Element #6): Risk-based due diligence
  5. Program Evaluation (Element #7): Use findings to adjust program
  6. Incident Response (Element #8): Prepare for likely incident scenarios
  7. Board Reporting (Element #9): Report top risks to board

Continuous Process: Risk assessment not one-time exercise; ongoing risk management

Examples

# Complete risk assessment guidance
/glba:risk-assessment all nist

# Planning phase for risk assessment
/glba:risk-assessment planning

# Execution guidance using qualitative methodology
/glba:risk-assessment execution qualitative

# Risk reporting templates and best practices
/glba:risk-assessment reporting

# Quantitative risk assessment approach
/glba:risk-assessment all quantitative

Risk Assessment Checklist

Planning:

  • Define assessment scope (systems, locations, processes)
  • Select methodology (NIST, ISO, qualitative, quantitative)
  • Assemble assessment team
  • Schedule assessment activities
  • Gather asset inventory

Execution:

  • Identify information assets
  • Identify threats (internal and external)
  • Identify vulnerabilities (technical, administrative, physical)
  • Assess likelihood of threat exploitation
  • Assess impact of successful threat exploitation
  • Evaluate existing controls
  • Calculate inherent and residual risk

Reporting:

  • Develop risk register
  • Create risk treatment plan
  • Prepare executive summary for board
  • Document methodology and findings
  • Communicate results to stakeholders

Follow-Up:

  • Track risk treatment implementation
  • Monitor high and critical risks
  • Update risk assessment annually or when changes occur
  • Report residual risks to board
  • Integrate findings into security program

GLBA Safeguards Rule Implementation

Provides detailed guidance on implementing the GLBA Safeguards Rule (16 CFR Part 314) information security program requirements.

Arguments

  • $1 - Focus area (required: all, risk-assessment, encryption, mfa, training, incident-response, vendor-management, board-reporting)
  • $2 - Institution size (optional: small, medium, large)

Safeguards Rule Overview

Authority: 16 CFR Part 314 Effective: June 9, 2023 (amended version) Applies to: Financial institutions subject to FTC jurisdiction Requirement: Comprehensive written information security program

Nine Required Elements

1. Designate Qualified Individual

Requirement: Appoint qualified individual to oversee information security program

Qualifications:

  • Appropriate knowledge and experience
  • Understands institution's systems and operations
  • Authority to implement security program

Responsibilities:

  • Develop and implement security program
  • Coordinate security controls
  • Report to board of directors
  • Oversee service providers

Implementation:

  • Formal designation letter or board resolution
  • Job description with security responsibilities
  • Adequate authority and resources
  • Technical expertise or access to experts

2. Risk Assessment

Requirement: Identify and assess reasonably foreseeable internal and external risks

Assessment Scope:

  • Internal threats (employees, contractors, business processes)
  • External threats (cyberattacks, natural disasters, service disruptions)
  • Information systems holding customer data
  • Physical locations where data is stored/processed

Assessment Process:

  1. Asset Identification: Inventory systems, data, and processes
  2. Threat Identification: Catalog potential threats
  3. Vulnerability Analysis: Identify weaknesses
  4. Likelihood Assessment: Probability of threat exploitation
  5. Impact Analysis: Potential damage from successful attack
  6. Control Evaluation: Assess existing safeguards
  7. Risk Calculation: Determine residual risk
  8. Documentation: Record findings and decisions

Frequency: Regular basis, at least annually or when significant changes occur

Output: Written risk assessment report

3. Design and Implement Safeguards

Requirement: Design and implement safeguards to control identified risks

Safeguard Categories:

Administrative Controls:

  • Policies and procedures
  • Security governance structure
  • Roles and responsibilities
  • Compliance monitoring
  • Third-party oversight

Technical Controls:

  • Access controls and authorization
  • Encryption (at rest and in transit)
  • Multi-factor authentication
  • Network security (firewalls, IDS/IPS)
  • Endpoint protection
  • Data loss prevention
  • Logging and monitoring
  • Vulnerability management
  • Secure development practices

Physical Controls:

  • Facility access control
  • Environmental protections
  • Media handling and disposal
  • Visitor management
  • Workstation security

4. Monitor and Test Safeguards

Requirement: Regularly monitor and test effectiveness of safeguards

Monitoring Activities:

  • Continuous security monitoring
  • Log review and analysis
  • Anomaly detection
  • Incident tracking
  • Compliance monitoring

Testing Activities:

  • Vulnerability scanning (quarterly or more)
  • Penetration testing (annual or risk-based)
  • Security control testing
  • Incident response drills
  • Business continuity testing
  • Disaster recovery testing

Frequency: Continuous monitoring, testing at least annually or when significant changes

5. Train Personnel

Requirement: Provide security awareness training to all personnel

Training Audience:

  • All employees (general awareness)
  • Privileged users (role-based training)
  • Executives and board (governance training)

Training Content:

  • GLBA requirements and importance
  • Information security policies
  • Phishing and social engineering
  • Password management
  • Incident reporting
  • Physical security
  • Privacy protection
  • Vendor management
  • Role-specific responsibilities

Frequency:

  • Initial training for new employees
  • Annual refresher training
  • Ad hoc training for policy changes or emerging threats

Documentation: Training attendance records, completion certificates, assessment results

6. Select Service Providers

Requirement: Exercise due diligence in selecting service providers and require them to implement safeguards

Service Provider Types:

  • Cloud service providers (IaaS, PaaS, SaaS)
  • Managed security service providers
  • Payment processors
  • Data storage vendors
  • Software vendors with access to customer data
  • Outsourced IT functions

Due Diligence Process:

  1. Security Assessment: Evaluate provider's security posture
  2. Risk Analysis: Determine risk level based on data access
  3. Certification Review: SOC 2, ISO 27001, etc.
  4. Contractual Protections: Include security requirements

Contract Requirements:

  • Implement appropriate safeguards
  • Protect confidentiality and integrity of customer information
  • Allow for monitoring and auditing
  • Notify of security incidents
  • Return or securely destroy data upon termination

Ongoing Oversight:

  • Periodic reviews of service providers
  • Monitor compliance with contract
  • Review audit reports (SOC 2, ISO audits)
  • Incident notification and response

7. Evaluate and Adjust Program

Requirement: Evaluate and adjust security program in light of monitoring, testing, and changes

Evaluation Triggers:

  • Results of monitoring and testing
  • Material changes to operations
  • New or evolving threats
  • Regulatory changes
  • Incidents and near-misses

Evaluation Process:

  1. Review risk assessment findings
  2. Analyze security incidents
  3. Assess control effectiveness
  4. Identify gaps and weaknesses
  5. Update safeguards as needed
  6. Document changes and rationale

Documentation: Program updates, change logs, board reports

8. Incident Response Plan

Requirement: Develop, implement, and maintain incident response plan

Plan Components:

1. Preparation:

  • Incident response team structure
  • Roles and responsibilities
  • Communication protocols
  • Tools and resources

2. Detection and Analysis:

  • Monitoring and alerting
  • Incident classification
  • Triage procedures
  • Evidence collection

3. Containment:

  • Immediate response actions
  • Short-term containment
  • Long-term containment
  • System isolation procedures

4. Eradication:

  • Root cause analysis
  • Threat removal
  • Vulnerability remediation

5. Recovery:

  • System restoration
  • Validation and testing
  • Return to normal operations

6. Post-Incident Activities:

  • Lessons learned analysis
  • Documentation
  • Reporting (internal and regulatory)
  • Improvement recommendations

Testing: Annual testing of incident response plan

Notification Requirements:

  • Customer notification (state breach laws)
  • Regulatory notification (if required)
  • Law enforcement (if criminal activity)
  • Service providers (if involved)

9. Encryption

Requirement: Encrypt customer information in transit and at rest

Encryption in Transit:

  • TLS 1.2+ for all web communications
  • SFTP/FTPS for file transfers
  • Encrypted email (S/MIME, PGP) for sensitive data
  • VPN for remote access
  • Encrypted API communications

Encryption at Rest:

  • Database encryption (TDE or field-level)
  • File system encryption
  • Full disk encryption for endpoints
  • Encrypted backups
  • Cloud storage encryption

Key Management:

  • Secure key generation
  • Key storage (HSM or key vault)
  • Key rotation policies
  • Access controls on keys
  • Key escrow/recovery procedures

Exceptions: Encryption not required if compensating controls provide equivalent protection and documented risk acceptance

Implementation by Institution Size

Small Institutions (<$5M revenue or <50 employees)

Simplified Approach:

  • Qualified individual may wear multiple hats
  • Risk assessment can be less formal
  • Commercial security products (SMB-focused)
  • Cloud services with strong security certifications
  • Outsource security functions to MSP/MSSP
  • Simplified documentation

Cost-Effective Solutions:

  • Microsoft 365 E3/E5 (includes encryption, MFA)
  • Google Workspace Enterprise
  • AWS/Azure with built-in security
  • Managed detection and response (MDR)
  • Security awareness platforms (KnowBe4, etc.)

Medium Institutions ($5M-$100M revenue)

Enhanced Controls:

  • Dedicated security personnel or consultant
  • Formal risk assessment methodology
  • Layered security controls
  • SIEM or log management
  • Vulnerability management program
  • Annual penetration testing

Technology Stack:

  • Endpoint detection and response (EDR)
  • Next-gen firewall
  • Email security gateway
  • DLP for high-risk data
  • Privileged access management

Large Institutions (>$100M revenue)

Mature Security Program:

  • CISO and security team
  • Comprehensive risk management framework
  • Advanced threat detection
  • Security operations center (SOC)
  • Continuous monitoring and testing
  • Formal governance structure

Enterprise Technologies:

  • SIEM with SOAR
  • Advanced threat protection
  • Zero trust architecture
  • Cloud access security broker (CASB)
  • Identity governance and administration

Common Implementation Challenges

  1. Encryption Gaps:

    • Legacy systems can't support encryption
    • Performance concerns
    • Key management complexity
    • Solution: Risk acceptance with compensating controls, system upgrades, encryption gateway
  2. MFA Resistance:

    • User friction
    • Technology limitations
    • Solution: Phased rollout, user training, modern authentication methods
  3. Resource Constraints:

    • Limited budget
    • Staff expertise gaps
    • Solution: Outsource to MSP/MSSP, leverage cloud security features, prioritize high-risk areas
  4. Vendor Management:

    • Hundreds of vendors
    • Vendor fatigue with security questionnaires
    • Solution: Tiered approach based on risk, accept certifications (SOC 2), vendor risk platforms
  5. Board Reporting:

    • Board lacks technical expertise
    • Unclear reporting requirements
    • Solution: Executive summaries with business impact, security metrics dashboards

Board Reporting Requirements

Frequency: At least annually Audience: Board of directors or equivalent governing body

Report Content:

  1. Program Overview: Security program status
  2. Risk Assessment Summary: Key risks and risk levels
  3. Safeguards Status: Implementation of nine elements
  4. Incidents: Security incidents and response
  5. Testing Results: Vulnerability scans, penetration tests
  6. Vendor Oversight: Service provider security status
  7. Compliance: Regulatory compliance status
  8. Budget and Resources: Security spending and resource needs
  9. Recommendations: Improvements and investments needed

Best Practices:

  • Use business language, not technical jargon
  • Quantify risk (financial impact)
  • Provide trend analysis
  • Include benchmarking data
  • Make actionable recommendations

FTC Guidance and Enforcement

FTC Resources:

  • Standards for Safeguarding Customer Information (final rule)
  • Data Security Made Simpler (business guidance)
  • Start with Security guide

Enforcement Focus:

  • Failure to implement MFA
  • Lack of encryption
  • Inadequate risk assessments
  • No incident response plan
  • Insufficient vendor oversight

Penalties:

  • Civil penalties per violation per day
  • Injunctive relief
  • Compliance monitoring
  • Individual liability for officers

Examples

# Complete Safeguards Rule implementation guidance
/glba:safeguards all medium

# Risk assessment methodology for small institution
/glba:safeguards risk-assessment small

# Encryption implementation guide
/glba:safeguards encryption

# MFA deployment guidance for large institution
/glba:safeguards mfa large

# Incident response plan development
/glba:safeguards incident-response

# Vendor management program
/glba:safeguards vendor-management

# Board reporting template
/glba:safeguards board-reporting

Sponsors

Details

Marketplace
GRCEngClub/claude-grc-engineering
Source
plugins/frameworks/glba
Category
Community

More from GRCEngClub/claude-grc-engineering

All 70