News

This article concludes a series about cloud security in existing Azure environments. Together, they reveal something more important: cloud security does not work as a collection of controls. It only works as a system.

Identity has become the silent backbone of every digital organization. Everything starts with access: users, applications, automation, and cloud resources all depend on it. Yet identity is often the least discussed topic in boardrooms, while at the same time it has become the most targeted attack surface.

This article is the fifth part in a series about cloud security within existing Azure environments. This section moves away from technical details and addresses a more challenging topic: ownership. Most cloud security issues arise not from absent controls but from unclear responsibilities.

The Network and Information Security Directive 2 (NIS2) requires organizations to implement measures to ensure the security and continuity of their IT environments.

We know you're not ready

I still remember participating in “failover tests” years ago (decades, actually — but let’s not dwell on that) for a financial institution, based on restoring data from tape. This was a company with over 300 physical servers, relying on time-consuming recovery from a sequential medium to bring back systems like Swift and large Oracle databases at a provider’s disaster recovery site.