Due Diligence and Ongoing Monitoring

 View Only
  • 1.  GLBA help...

    Posted 10-07-2019 10:36 AM
    ​​Good morning,

    In a recent internal audit, GLBA was the focus. GLBA requires our Credit Union to have implemented programs to oversee and confirm that service providers are meeting the law. Our program needs to specifically address the requirements for all vendors to comply with GLBA, and all applicable laws, regulations and standards. It was noted that NYS has introduced the SHIELD Act which will require any organization with NYS residential data to meet additional guidelines.  

    It was recommended that a checklist should be relied on to ensure that the controls covered within SOC reports provide sufficient comfort that the vendors are meeting the expectations of GLBA.

    Does anyone have a GLBA checklist they could share, or ideas for constructing one?



  • 2.  RE: GLBA help...

    Posted 10-07-2019 05:12 PM

    It sounds like your Internal Audit team is asking for a plan to review SOC reports annually.  Which is certainly a best practice.  This is normally accomplished by establishing a document collection and review calendar for your credit union.

    GLBA 501 (b) asks financial institutions to have type of assurance from their vendors that they are maintaining the Confidentiality, Integrity and Availability triangle when it comes to your customer's data.

    That is normally handled with a soc report.  Personally, i look for a SSAE 18 soc 2 type 2.  Though a SOC type 3 is a good report to have from any vendor.  These reports look at the following criteria in detail to ensure your vendor is taking care of cybersecurity in a reasonable manner. Soc reports test controls around server security, network security, access controls, patch management (which assumes some form of vulnerability assessment), backup management, log file management, least privilege, and third party assessments (penetration testing, third party vulnerability scanning and third party security monitoring).

    I go through all this to make this point.  You will need to identify someone with credentials in information security or information systems auditing to interpret the reports.  There are several credentials that attest to a person's ability to interpret these reports; two examples are the CISSP and the CISA certifications.

    Has anyone established a document collection schedule/calendar and review schedule/calendar for SOC reports?




  • 3.  RE: GLBA help...

    Posted 10-08-2019 08:55 AM
    We review SOC 2 Type 2 reports for vendors providing cloud solutions (SaaS, IaaS) and with whom we share Confidential information..  We keep a schedule based on the date the SOC report was issued by the independent auditor, generally this is on an annual basis.  We do not keep a specific checklist, but we do map any Complementary Users Entity Controls indicated in the SOC report to our own controls.


  • 4.  RE: GLBA help...

    Posted 10-08-2019 09:15 AM
    ​Good morning,

    We do have a very structured review process.  High and critical vendors are reviewed on a yearly basis, this includes any vendor critical to operation and or has access to PII/NPI.  This does include due diligence collection, updated vendor questionnaires, Risk Assessment, SOC analysis, CUEC's reviewed for updates and completed.

    This year they are specifically looking for a formal checklist, I was hoping that someone had one they could share.


  • 5.  RE: GLBA help...

    Posted 01-08-2020 12:46 PM
    Yes as part of our onboarding and/or periodic review process, the due diligence package for all cloud vendors or Critical/High rated vendors requires a SOC to be collected and reviewed by our Information Security team BEFORE the contract/service agreement is signed with the vendor.  These type of vendors are reviewed yearly.   The IS team reviews the content of the SOC report (whether it be a SSAE 18, or SOC 2 Type 2), and then reviews each of the controls with the vendor relationship manager to ensure proper controls are in place for the service/product being provided by the vendor.  Any High risk controls discovered thru this conversation is reviewed by our Enterprise Risk Management Committee to determine if the risk is accepted or additional mitigation is required and a plan to do so is documented.