If you’re helping shape application security in an organization, whether as an external security consultant or vendor, or as part of an internal security team, it is critical to work effectively with developers. While a lot of individuals have an interest and stake in security, and many have a significant role to play, developers who write code and fix flaws determine whether application security initiatives succeed or fail.

On September 14, the White House released Executive Order M-21-30, emphasizing and reminding us that there are NIST guidelines for securing any software being sold to the US Government. According to the Executive Order (EO), self-attestation is a requirement for software vendors or agencies and acts as a “conformance statement” outlined by the NIST Guidance.

The last few years have seen a huge shift in how organizations work with their data. The COVID pandemic accelerated a digital transformation as workers transitioned from the office to home-based and back into hybrid working environments. With this new set-up, collaboration is key to worker efficiency. However, the adoption of Microsoft 365 and Teams as a front-end platform has created new challenges for security teams.

Fleet operations today revolve around data. Telematics systems, connected cars, and similar IoT systems provide fleet managers with a wealth of information, but this connectivity also raises security concerns. As data breach costs reach their highest point in decades, accounting for vulnerabilities in organizations’ data becomes increasingly crucial. Data-rich and notoriously difficult-to-secure fleets are no exception.