Blog

What’s the Difference Between SOC for Cybersecurity and SOC 2?

May 22, 2018/0 Comments/in Blog /by Jenna Kersten

The AICPA recently added a new offering to its SOC suite: SOC for Cybersecurity. The difference between SOC 1, SOC 2, and SOC 3 has always been fairly clear-cut, but now it’s getting a little more complicated. Want help deciding if a SOC for Cybersecurity engagement is right for your organization?

Auditor Insights: Security at Data Centers

May 17, 2018/0 Comments/in Blog /by Mike Wise

Even with the shift to cloud-based infrastructure, data centers are still the critical physical point for protecting critical data from physical theft. Learn best practices for physical security at data centers from Mike Wise, Information Security Specialist at KirkpatrickPrice.

The Purpose of SOC for Cybersecurity

May 15, 2018/0 Comments/in Blog /by Jenna Kersten

Managing cybersecurity risks is challenging, even with a sophisticated cybersecurity risk management program. Organizations should do everything possible to prevent, detect, and mitigate cybersecurity risks. Could your organization benefit from a SOC for Cybersecurity examination? Let’s find out.

Auditor Insights: Business Continuity and Disaster Recovery Plans for the Cloud

May 10, 2018/0 Comments/in Blog /by Michael Burke

Most business owners understand the importance of Business Continuity and Disaster Recovery Plans. These documented sets of policies and procedures can be a lifeline to organizations following a disaster because they determine loss of operations, reputation, and revenue. But how does the cloud impact Business Continuity and Disaster Recovery Plans?

[24]7.ai Cyber Incident: How Your Vendors Can Impact Your Security

May 8, 2018/0 Comments/in Blog /by Jenna Kersten

Earlier this month, [24]7.ai announced a cyber incident that occurred between September 26 and October 12, 2017. Never heard of [24]7.ai? We hadn’t either, but their well-known clients gave this breach national attention. Sears, Delta Air Lines, and Best Buy have all announced breaches traced back to [24]7.ai.