Cyberark issued a new report about reducing the cyber security risk when implementing DevOps. [shutterstock.com: 116202553, m00osfoto]
[shutterstock.com: 116202553, m00osfoto]
DevOps Press Release

DevOps: New Report Shows How To Reduce Security Risk

CyberArk, expert on privileged access security, issued a new research report, “The CISO View: Protecting Privileged Access in DevOps and Cloud Environments.”

Based on the direct experiences of a panel of Global 1000 CISOs, the report provides advice for security teams to help effectively assess risk, drive developer collaboration, and prioritize steps to protect DevOps processes while maintaining developer velocity.

The report is part of The CISO View industry initiative and features contributions from executives at leading organizations who are adopting DevOps methodologies and tools, including American Express Company, American Financial Group, Asian Development Bank, CIBC, ING Bank, Lockheed Martin, NTT Communications, Pearson, and also Starbucks.

Sponsored by CyberArk, the initiative brings together leading CISOs for peer-to-peer information. They are sharing experiences and thoughts to consequently help security teams build effective cyber security programs.

Undoubtedly, security strategies should address privileged access and the risk of unsecured secrets and credentials. However, they should also closely align with DevOps culture and methods to avoid negatively impacting developer velocity and slowing the release of new services. Despite this, 73 percent of organizations surveyed for the 2018 CyberArk Global Advanced Threat Landscape report have no strategy to address privileged access security for DevOps.

Recommendations

The report summarizes five key recommendations based on the real-world experiences of participating CISOs.

  1. Transform the security team into DevOps partners. Ensure security practitioners and developers have the right skills. Make it easy for developers to do the right thing. Encourage collaboration and, furthermore, adopt agile DevOps methods within security.
  2. Prioritize securing DevOps tools and infrastructure. Set and enforce policies for tools selection and configuration. Control access to DevOps tools. Ensure least privilege and also protect and monitor infrastructure.
  3. Establish enterprise requirements for securing credentials and secrets. Mandate the centralized management of secrets. Extend auditing and monitoring capabilities. Eliminate credentials from tools and applications. Develop reusable code modules.
  4. Adapt processes for application testing. Integrate automated testing of code. Compel developers to fix security issues using a “break the build” approach. Consider a bug bounty program.
  5. Evaluate the results of DevOps security programs. Test secrets management solution deployments. Measure and promote improvements. Moreover, educate auditors.

“This CISO View report captures the experiences and recommendations of senior executives who are securely embracing DevOps workflows, said Marianne Budnik, CMO, CyberArk. “For organizations embarking on digital transformation initiatives, it has never been more important to align security and risk postures across new tools and technologies. In understanding organizational and operational challenges, security teams can more effectively drive productive discussions across executive, security and also developer teams.”

Source:
Cyberark

About the author

E-3 Magazine

Articles published through E-3 Magazine International. This includes press releases by our partners as well as articles and reports from the E-3 team of journalists.

Add Comment

Click here to post a comment

ad_banner

ad_banner
Our Authors