.png){kind=logo}
Instructor
Blaise is a Director at A-LIGN and has over 15 years of experience in Security Compliance and Risk Management. He joined A-LIGN in 2013 and started the HITRUST/HIPAA and Healthcare Services practice in 2015. Having a very unique background as a CPA, CISA and CCSK, Blaise has performed over 500 SOC attestation reviews and over 300 HITRUST/HIPAA assessments for Global 1000 and Fortune 500 clients in various industries. Blaise is also a sought-after speaker and has delivered several speaking engagements at well-renowned conferences such as HIMSS, HITRUST, and ISACA. Blaise has also written dozens of blogs and whitepapers on the topics of Security Compliance, Telemedicine, Blockchain technology, and Third-Party Risk Management. Prior to joining A-LIGN, Blaise was a Senior Consultant at Century Payments, Inc., and an Advisory Associate at KPMG.
Organizations that provide services to other entities need a way to manage risks associated with outsourcing those services. The original standard for reducing that risk was known as a SAS 70 Attestation which was performed by a CPA. The result was a report used to demonstrate the effectiveness of internal controls over financial reporting. Organizations began to use the report as evidence that a vendor was secure and safe to work with. When the SSAE 16 report was introduced, it was renamed Systems and Organization Controls 1 (SOC 1) and continued to address financial criteria. SOC 2 was created at the same time to specifically address security, privacy, availability, integrity, and confidentiality. In other words, everything else that doesn't affect financial reporting. If your organization hosts financial information or has a system or process that impacts the financial statements of a client, then SOC 1 is for you. If you are a third-party provider with a system used by other organizations, a SOC 2 Attestation could be requested from you. It's not uncommon to need both SOC 1 and 2 Attestation reports. Investors, auditors, business partners, vendors, clients, and prospects are example parties that will typically rely on the SOC 1 and or SOC 2 Attestation reports. Software vendors, payroll providers, collection companies, data centers, cloud providers, managed service providers, CPA firms, HR firms, law firms, and consulting firms, just to name a few, are example of organizations that might be required to perform a SOC 1 and or SOC 2 Attestation. In this webinar, attendees will learn more about how to get ready for a SOC 1 and SOC 2 assessment and how to use the reports.
1. Why SAS 70 evolved into SOC 1 and SOC 2 audit reports.
2. Why partners, investors and vendors ask for SOC audits.
3. What types of organizations are good candidates for SOC audits.
4. How to prepare for SOC audits.
5. How stakeholders should use the reports.
SOC 1 and SOC 2 Attestation Engagements
None
None
CPAs that issue, use or rely on SOC 1 and or SOC 2 Attestation Reports Investors or other stakeholders that rely on SOC 1 and or SOC 2 Attestation Reports
.jpg){kind=logo}