| Regulatory Compliance Overview |
| GLBA |
| PCI DSS |
| SOX |
| USA PATRIOT Act |
| Dodd-Frank Act |
| ISO 27001 |
| COBIT |
| HIPAA |
| NERC |
Ask the Experts
Submit a no-obligation question about GLBA compliance.
LEARN MORE: Stay up to date on GLBA compliance issues & changes. Join us on FaceBook, Twitter, and the InfoSight Blog.
With rapid changes in technology, such as advances in mobile and Web 2.0 solutions, protecting customer information continues to be a challenge. For example, GLBA compliance requires us to analyze the risks before moving customer information into emerging technology models such as voice over IP (VoIP) systems or cloud computing. Clearly, organizations would be well served to invest time and effort early in the process to identify and assess observable risks in any new technology that processes customer data. This is where InfoSight can help.
Section 501(b) of the Gramm-Leach-Bliley Act (GLBA) contains important provisions aimed at the protection of information including data in both electronic and non-electronic formats. Protecting information assets is necessary to establish and maintain trust between the financial institution and its customers, maintain compliance with the law, and protect the reputation of the institution. The primary goals of a GLBA Compliance Assessment are to:
Complementary Services
IT Audit / Compliance Assurance Program
GLBA Risk Assessment
Enterprise Risk Management

What is
GLBA Compliance?
The Gramm-Leach-Bliley Act (GLBA), also known as the Financial Modernization Act of 1999, is aimed at financial institutions and is enforced by eight separate federal agencies and the states. Gramm-Leach-Bliley (GLBA) provides for a fairly broad interpretation of the phrase "financial institution" and not only affects banks, insurance companies, and security firms, but also brokers, lenders, tax preparers, and real estate settlement companies, among others.
Do you have something to add to this definition? Let us know.Email your comments and contributions.