Regulatory Compliance for Financial Institutions: Implementation of a GLBA-Complaint Information Security Program
The objective of this work in writing is to examine the implementation of a GLBA-complaint information security program.
Objectives of the Information Security Program
The Gramm-Leach-Bliley Act (GLBA) makes a requirement of financial institutions to "develop, implement, and maintain a comprehensive written information security program that protects the privacy and integrity of customer records. GLBA mandates emphasize the need for each bank, thrift, and credit union agency to adopt a proactive information security and technology risk management capability. By doing so, your institution can protect information, applications, databases, and the network as part of a comprehensive information security program." (Net Forensics, 2012, p.1)
Financial institutions are required by banking regulators to "evolve beyond point-security products. You must employ an integrated security strategy that establishes perimeter security as well as security inside the network and among all databases, applications, and end-point devices such as laptops, PCs, wired and wireless devices, PDAs, and more." (Net Forensics, 2012, p.1) All devices on the network are required to collaborate "to ensure proactive security is working effectively." (Net Forensics, 2012, p.1)
In addition all devices must be adaptable in real-time to the changing profile risk and new threats to security as they happen. (Net Forensics, 2012, p., paraphrased) The FDIC reports that the Interagency Guidelines Establishing Information Security Standards (Guidelines) "set forth standards pursuant to section 39 of the Federal Deposit Insurance Act, 12 U.S.C. 1831p -- 1, and sections 501 and 505(b), 15 U.S.C. 6801 and 6805(b), of the Gramm-Leach-Bliley Act. These Guidelines address standards for developing and implementing administrative, technical, and physical safeguards to protect the security, confidentiality, and integrity of customer information. These Guidelines also address standards with respect to the proper disposal of consumer information pursuant to sections 621 and 628 of the Fair Credit Reporting Act (15 U.S.C. 1681s and 1681w)." (2000, p.1)
III. Scope of the Information Security Program
According to the FDIC, the guidelines are applicable to customer information that is maintained "by or on behalf of, and to the disposal of consumer information by or on the behalf of, entities over which the Federal Deposit Insurance Corporation (FDIC) has authority. Such entities, referred to as "the bank" are banks insured by the FDIC (other than members of the Federal Reserve System), insured state branches of foreign banks, and any subsidiaries of such entities (except brokers, dealers, persons providing insurance, investment companies, and investment advisers)." (2000, p.1)
IV. Oversight and Delivery of the Information Security Program
Stated as the arrangement for overseeing service provider arrangements are that each bank shall:
(1) Exercise appropriate due diligence in selecting its service providers;
(2) Require its service providers by contract to implement appropriate measures designed to meet the objectives of these Guidelines; and (3) Where indicated by the bank's risk assessment, monitor its service providers to confirm that they have satisfied their obligations as required by paragraph D.2. As part of this monitoring, a bank should review audits, summaries of test results, or other equivalent evaluations of its service providers. (FDIC, 2000, p.1)
V. Information Security Program Overview
The Information Security Program involves each bank implementing a "comprehensive written information security program that includes administrative, technical, and physical safeguards appropriate to the size and complexity of the bank and the nature and scope of its activities." (FDIC, 2000, p.1) A uniform set of policies is not required to be implemented by all parts of the bank it is required that all elements of the information security program are coordinated. The bank's information security program should be designed in such a way that:
(1) Ensures the security and confidentiality of customer information;
(2) Protects against any anticipated threats or hazards to the security or integrity of such information;
(3) Protects against unauthorized access to or use of such information that could result in substantial harm or inconvenience to any customer; and (4) Ensures the proper disposal of customer information and consumer information. (FDIC, 2000, p.1)
VI. Identification and Classification of Information Security
Customer information includes "any record containing nonpublic personal information about a customer of a financial institution, whether in paper, electronic, or other form, that is handled or maintained by or on behalf of the financial institution or its affiliates." (Purdue University, 2000) Non-public personal information means financial information personally identifiable that is:
(1) Provided by a consumer to a financial institution;
(2) Resulting from any transaction with the consumer or any service performed for the consumer; or (3) Otherwise obtained by the financial institution. (Purdue University, 2000)
This also includes "…any list, description, or other grouping of consumers and publicly available information pertaining to them that is derived using any personally identifiable financial information...
Our semester plans gives you unlimited, unrestricted access to our entire library of resources —writing tools, guides, example essays, tutorials, class notes, and more.
Get Started Now