The Schellman Blog

Microsoft’s Supplier Security and Privacy Assurance (SSPA) program received a major update with Version 10, which took effect on September 23rd, 2024. This update introduced new requirements, particularly around artificial intelligence (AI) and ISO 42001 compliance.

Schellman's Danny Manimbo and Healthcare Assessment leader, Ryan Meehan, discuss in under 3 minutes what you need to know about the proposed changes to the HIPAA Security Rule.

Hi, I'm Stu Block the Sustainability Practice Director here at Schellman. We provide our clients with sustainability services in three primary areas. 1. Sustainability Regulatory Reporting Readiness

Looking back, 2024 was the year of AI governance. At Schellman, we dove in headfirst and became the first ANAB ISO 42001-accredited Certification Body. We also started to see AI regulation come online internationally with the EU AI Act, as well as here in the U.S., where certain states also published their own AI regulation. While we're still lacking federal-level legislation—which may still come in the future—we also anticipate that this state-by-state patchwork of AI laws will expand.

Let's talk about GHG emissions and how they are reported according to the Greenhouse Gas Protocol by categorizing them into three scopes. Scope 1 GHG Emissions

Payment, script, security, controls. Did any of those make you feel warm and fuzzy? Probably not.

As one of the largest cybersecurity assessment firms in the world, Schellman provides services like ISO, FedRAMP, SOC, and PCI. In parallel with the compliance and technology space that continues to evolve, we've adapted our ISO services, including acquiring dual accreditation from ANAB and UKAS to meet the ever-evolving needs of our clients.

(Schellman CEO) Avani Desai here. Let's talk about something that can make or break your business...DORA. Otherwise known as the Digital Operational Resilience Act, DORA is set to redefine how financial institutions and their critical third-party providers manage digital threats.

If you’ve not yet heard, the NIS2 Directive—an increasingly critical cybersecurity regulation for organizations across the EU—is set to go into effect on October 17th. That means that Member States must adopt and publish the necessary cybersecurity measures by October 17, 2024, and apply them from October 18, 2024, onward—so, is your organization ready?

Hi, I'm Matt Crane. I'm a leader in the payment security practice here at Schellman. We're often asked if we're able to do both PCI assessments and penetration testing for the same client. In this video, we'll explain how we're able to provide both and why it's not an independence issue. First and foremost, I want to cover what the PCI Council says about this. While they don't specifically state that it is or is not an independence issue, if you look at Requirement 11.4 of PCI DSS v4.0, it talks about penetration testing services methodologies. The two main criteria that you have to have as a penetration tester to meet that requirement are: You have organizational independence, which means that the individual performing the test cannot be ultimately responsible for securing that system. (It goes on to say that organizational independence doesn't mean it has to be an ASV or approved scanning vendor or even a QSA, but so long that that individual doesn't have control over the systems they're testing, it's fine. So, if you have an internal resource that's qualified, you can move forward with them.)