News and blog
NXLog main page
  • Products
    NXLog Platform
    Log collection
    Log management and analytics
    Log storage
    NXLog Community Edition
    Integrations
    Professional Services
  • Solutions
    Use cases
    Specific OS support
    SCADA/ICS
    Windows event log
    DNS logging
    MacOS logging
    Open Telemetry
    Solutions by industry
    Financial Services
    Government & Education
    Entertainment & Gambling
    Telecommunications
    Medical & Healthcare
    Military & Defense
    Law Firms & Legal Counsel
    Industrial & Manufacturing
  • Pricing
    Licensing
    Plans
  • Partners
    Find a Reseller
    Partner Program
    Partner Portal
  • Resources
    Documentation
    Blog
    White papers
    Videos
    Webinars
    Case Studies
    Community Program
    Community Forum
  • About
    Company
    Careers
  • Support
    Support portals
    Contact us

NXLog Platform
Log collection
Log management and analytics
Log storage
NXLog Community Edition
Integrations
Professional Services

Use Cases
Specific OS support
SCADA/ICS
Windows event log
DNS logging
MacOS logging
Open Telemetry
Solutions by industry
Financial Services
Government & Education
Entertainment & Gambling
Telecommunications
Medical & Healthcare
Military & Defense
Law Firms & Legal Counsel
Industrial & Manufacturing

Licensing
Plans

Find a Reseller
Partner Program
Partner Portal

Documentation
Blog
White papers
Videos
Webinars
Case Studies
Community Program
Community Forum

Company
Careers

Support portals
Contact us
Let's Talk
  • Start free
  • Interactive demo
Let's Talk
  • Start free
  • Interactive demo
NXLog search
  • Loading...
Let's Talk
  • Start free
  • Interactive demo
January 23, 2024 compliancestrategy

GLBA Compliance in 2024 - Reporting directly to the FTC

By Roman Krasnov

Share
ALL ANNOUNCEMENT COMPARISON COMPLIANCE DEPLOYMENT SECURITY SIEM STRATEGY RSS

The U.S. Federal Trade Commission (FTC) approved amendments to its Safeguards Rule that require FTC-regulated non-banking financial institutions to report data breaches and other security events directly to the FTC. It was originally proposed to add a breach notification requirement back in late 2021. The rule requires financial institutions to report “notification events” to the FTC within 30 days of discovery of the notification event where the private information of 500+ consumers is involved. The FTC has also indicated that it will make incident reports publicly available and non-banking financial institutions are expected to be prepared for increased media exposure and litigation risk.

The final amendment was published on November 13, 2023, and will take effect on May 13, 2024, according to the Federal Register. Let’s see how an effective log collection solution can contribute to your Gramm-Leach-Bliley Act (GLBA) compliance strategy in 2024.

What is the Safeguards Rule?

“Standards for Safeguarding Customer Information Rule” is a part of the Financial Modernization Act of 1999, known as The Gramm-Leach-Bliley Act (GLBA) - a US federal law that requires financial institutions “to explain their information-sharing practices to their customers and to safeguard sensitive data“. It’s an example of early legislation enacted to ensure transparent and secure handling of customer’s private information.

The Safeguards Rule took effect in 2003 and was first amended in 2021 to match the level of modern technologies. The rule is general in scope and reflects common data security principles that companies need to implement to protect the Nonpublic Personal Information (NPI) of their customers (name, address, income, Social Security number, payment history, loan or deposit balances, and credit or debit card purchases).

Nonpublic Personal Information means:

(i) Personally identifiable financial information; and (ii) Any list, description, or other grouping of consumers (and publicly available information about them) that is derived using any personally identifiable financial information that is not publicly available.

The FTC provides details and examples of NPI with additional articles available as business guidance.

Coverage and Penalties

The Safeguarding Rule applies to financial institutions subject to the FTC’s jurisdiction and that aren’t subject to the enforcement authority of another regulator under section 505 of the Gramm-Leach-Bliley Act, 15 U.S.C. § 6805. According to Section 314.1(b), an entity is a “financial institution” if it’s engaged in an activity that is “financial in nature” or is “incidental to such financial activities”:

Financial institution means any institution the business of which is engaging in an activity that is financial in nature or incidental to such financial activities as described in section 4(k) of the Bank Holding Company Act of 1956, 12 U.S.C § 1843(k). An institution that is significantly engaged in financial activities, or significantly engaged in activities incidental to such financial activities, is a financial institution.

While the term is quite broad, the rule provides some direct guidance on what companies are covered by the regulation. According to 16 CFR 314.2(h), the following entities are obligated to comply with the GLBA Safeguards Rule:

  • Automobile dealerships

  • Real estate settlement services

  • Mortgage brokers

  • Travel agencies in financial services

  • Retailers issuing credit cards

  • Property appraisers

  • Career counselors

  • Check printing businesses

  • Money transfer services

  • Check cashing businesses

  • Tax preparation services

  • Investment and credit counseling services

  • Higher education institutions

It’s worth noting that a financial institution company may be exempt from certain requirements if it maintains fewer than 5,000 consumer records.

GLBA imposes penalties for non-compliance on organizations that fail to adhere to the law’s requirements. In addition to reputation damage, the penalties for non-compliance include:

  • Civil Penalties: The GLBA authorizes the FTC to impose civil penalties on financial institutions that violate the law’s privacy and security requirements. The maximum penalty for each violation is $100,000.

  • Criminal Penalties: The GLBA includes criminal penalties for financial institutions that knowingly and willfully violate the requirements. These penalties can include fines of up to $10,000 for each violation and imprisonment for up to 5 years.

There are a set of cases where the FTC fined financial institutions for GLBA non-compliance. The most notable notices were against PayPal in 2018 and crypto services provider Celsius Networks in 2023 reaching a total of $4.7B in fines.

Requirements

According to 16 CFR 314.4, in order to develop, implement, and maintain an information security program, an institution shall perform several steps, including:

  • (a) Designate a Qualified Individual responsible for overseeing, implementing, and enforcing your information security program.

  • (c) Design and implement safeguards to control the risks identified, including:

    • (1) Implement and periodically review access controls

    • (3) Protect by encryption all customer information held or transmitted

    • (8) Implement policies, procedures, and controls designed to monitor and log the activity of authorized users and detect unauthorized access or use of, or tampering with, customer information by such users.

  • (d)

    • (1) Regularly test or otherwise monitor the effectiveness of the safeguards

    • (2) For information systems, the monitoring and testing shall include continuous monitoring or periodic penetration testing and vulnerability assessments.

  • (h) Establish a written incident response plan designed to promptly respond to, and recover from, any security event.

  • (i) Require your Qualified Individual to report in writing, regularly and at least annually, to your board of directors or equivalent governing body. The report shall include the following information:

    • (1) The overall status of the information security program and your compliance with this part; and

    • (2) Material matters related to the information security program, addressing issues such as risk assessment, risk management and control decisions, service provider arrangements, results of testing, security events or violations and management’s responses thereto, and recommendations for changes in the information security program.

How can NXLog help?

Log collection is a key part of any modern cybersecurity program. Proper log collection enables core security processes like monitoring, incident response, and reporting. NXLog helps organizations stay compliant by providing a centralized security observability solution. With NXLog, you can build a robust log collection architecture and analyze logs across disparate systems to boost threat detection, minimize response time, and ensure you always stay compliant with regulations.

  • Enable audit log centralization with nothing missed

NXLog supports all popular and advanced log data collection methods. It seamlessly integrates with various data sources, including databases, network appliances, SIEM, and APM systems to ensure a compliant log management process.

  • Simplify processes with unified log collection infrastructure

NXLog allows an organization to define a unified log collection mechanism across an entire infrastructure, including system and operational components. Unified log collection helps design comprehensive technical solutions and simplify routines and policies that must be documented and communicated to staff.

  • Keep data safe while in transfer

Log data may include sensitive information, like NPI. To make transfers secure, NXLog provides TLS/SSL encryption support to prevent data in transit from being viewed or modified by a malicious actor.

  • Enforce audit log & system file monitoring against unauthorized changes

NXLog provides a File Integrity Monitoring (FIM) module that detects when files are changed and promptly triggers a security event. This helps to protect both critical system files and retained logs from unauthorized tampering.

  • Enable cost-efficient audit log retention

Nowadays, IT systems generate tons of logs and audit trails. All that data has to be available for real-time analysis and also capable of being quickly re-hydrated from long-term storage for faster response in the case of a security event. NXLog provides log filtration, flexible retention, and routing mechanisms, creating a robust and cost-efficient retention process.

NXLog Platform is an on-premises solution for centralized log management with
versatile processing forming the backbone of security monitoring.

With our industry-leading expertise in log collection and agent management, we comprehensively
address your security log-related tasks, including collection, parsing, processing, enrichment, storage, management, and analytics.

Start free Contact us
  • compliance
  • legislation
Share

Facebook Twitter LinkedIn Reddit Mail
Related Posts

The story of the $1,900,000 penalty for insufficient log management
4 minutes | January 11, 2024
How to prevent and detect Log4j vulnerabilities
6 minutes | February 3, 2022
Understanding and auditing WMI
18 minutes | January 25, 2022

Stay connected:

Sign up

Keep up to date with our monthly digest of articles.

By clicking singing up, I agree to the use of my personal data in accordance with NXLog Privacy Policy.

Featured posts

Security dashboards go dark: why visibility isn't optional, even when your defenses keep running
February 26, 2026
Building a practical OpenTelemetry pipeline with NXLog Platform
February 25, 2026
Announcing NXLog Platform 1.11
February 23, 2026
Adopting OpenTelemetry without changing your applications
February 10, 2026
Linux security monitoring with NXLog Platform: Extracting key events for better monitoring
January 9, 2026
2025 and NXLog - a recap
December 18, 2025
Announcing NXLog Platform 1.10
December 11, 2025
Announcing NXLog Platform 1.9
October 22, 2025
Gaining valuable host performance metrics with NXLog Platform
September 30, 2025
Security Event Logs: Importance, best practices, and management
July 22, 2025
Enhancing security with Microsoft's Expanded Cloud Logs
June 10, 2025

Categories

  • ANNOUNCEMENT
  • COMPARISON
  • COMPLIANCE
  • DEPLOYMENT
  • SECURITY
  • SIEM
  • STRATEGY
  • Products
  • NXLog Platform
  • NXLog Community Edition
  • Integration
  • Professional Services
  • Licensing
  • Plans
  • Resources
  • Documentation
  • Blog
  • White Papers
  • Videos
  • Webinars
  • Case Studies
  • Community Program
  • Community Forum
  • Compare NXLog Platform
  • Partners
  • Find a Reseller
  • Partner Program
  • Partner Portal
  • About NXLog
  • Company
  • Careers
  • Support Portals
  • Contact Us

Follow us

LinkedIn Facebook YouTube Reddit
logo

© Copyright NXLog Ltd.

Subscribe to our newsletter

Privacy Policy • General Terms of Business