Sysdig Announces Sysdig Secure 2.0
June 14, 2018

Sysdig introduced Sysdig Secure 2.0, a way for enterprises to secure containers and microservices.

The latest version adds vulnerability management, more than two hundred compliance checks, and security analytics. The Sysdig Cloud-Native Intelligence Platform is the only technology to offer unified security, monitoring, and forensics for containers and microservices, giving users a robust view of the health and risk profiles of their cloud-native applications.

Sysdig Secure’s vulnerability management capabilities help organizations bring application security, compliance, and quality closer to the developer. Sysdig Secure ensures that as companies scale, their security scales at the same rate, allowing DevOps to deploy knowing all images and containers are vulnerability free, the microservices are in compliance, and they can defend their applications from compromise.

Vulnerability Management:

- Static image scanning – Sysdig Secure 2.0 can parse container images and identify vulnerable packages, libraries, and configurations before a deployment, ultimately enabling a more secure environment and driving consistent processes across development teams.

- CI/CD integrations – Sysdig Secure 2.0 adds a native Jenkins plugin, which adds a Sysdig Secure step to the CI pipeline and enables companies to automate container image scanning. With each fail build, the system automatically evaluates the image against policy and forces compliance before an image progresses in the pipeline.

- Quarantine or kill vulnerable images – Sysdig Secure 2.0 can take actions like killing or quarantining a container if vulnerabilities or exposed credentials are found, reducing the risk of a security breach.

- Runtime vulnerability management and scanning – Sysdig Secure 2.0 manages, tracks, and updates vulnerability data for containers in production. Sysdig Secure 2.0 also enriches it with Kubernetes metadata to provide context when fixing vulnerabilities across distributed applications.

Compliance:

- Sysdig Secure 2.0 eases the pain of measuring and enforcing compliance across a distributed environment through compliance controls, audit checks, policies, and results.
- Sysdig automatically scans the infrastructure with requirements based on Center for Internet Security (CIS) configurations and hardening benchmarks. Sysdig allows users to scope and schedule Docker and Kubernetes benchmarks to measure and maintain compliance.

Security Analytics:

Effective container runtime security hinges on security response teams being able to quickly detect, analyze, and respond to security threats on live containers – from detection, to remediation, to forensics. Sysdig Secure 2.0 provides rich metrics about events, compliance, and vulnerabilities over time, enabling deeper analytics and a better understanding of the environment. Security metrics tied back to containers, images, hosts, and Kubernetes entities enable users to easily determine how different organizations, applications, and services are trending in the security posture.

“Due to the newness of containers and the dynamic environment, container security for cloud-native applications poses several new challenges,” said Loris Degioanni, CTO and founder, Sysdig. “Sysdig Secure 2.0 ensures that developers, operations, and risk professionals have a single source of intelligence to monitor and secure their applications.”

Sysdig Secure is available as a standalone technology or as a part of the unified Sysdig Cloud-Native Intelligence Platform, which includes Sysdig Monitor. Sysdig Secure 2.0 is currently available as a private beta.

The Latest

July 19, 2018

Despite 95 percent of CIOs expecting cyberthreats to increase over the next three years, only 65 percent of their organizations currently have a cybersecurity expert, according to a survey from Gartner. The survey also reveals that skills challenges continue to plague organizations that undergo digitalization, with digital security staffing shortages considered a top inhibitor to innovation ...

July 17, 2018

In my first blog in this series, I highlighted some of the main challenges teams face with trying to scale mainframe DevOps. To get past these hurdles, the key is to develop an incremental approach that enables teams to capture value along each step of the journey ...

July 16, 2018

The key to mainframe DevOps success is in quickly identifying and removing major bottlenecks in the application delivery lifecycle. Major challenges include collaboration between mainframe and distributed teams, lack of visibility into the impact of software changes, and limited resource flexibility with scaling out necessary testing initiatives. Now let's take a closer look at some of these key challenges and how IT departments can address them ...

July 11, 2018

How much are organizations investing in the shift to cloud native, how much is it getting them? ...

July 10, 2018

In the shift to cloud native, many organizations have adopted a configuration-as-code approach. This helps drive up application deployment velocity by letting developers and DevOps teams reconfigure their deployments as their needs arise. Other organizations, particularly the more regulated ones, still have security people owning these tools, but that creates increased pressure on the security organization to keep up. How much are organizations investing in this process, and how much is it getting them? ...

June 28, 2018

More than a third of companies that use serverless functions are not employing any application security best practices and are not using any tools or standard security methodologies to secure them, according to the State of Serverless Security survey, conducted by PureSec ...

June 27, 2018

The popularity of social media platforms and applications is spurring enterprises to adopt "social business" models to better engage with employees and customers and improve collaboration, according to a new study published by ISG ...

June 25, 2018

The previous chapter in this WhiteHat Security series discussed Codebase as the first step of the Twelve-Factor App and defined a security best practice approach for ensuring a secure source control system. Considering the importance of applying security in a modern DevOps world, this next chapter examines the security component of step two of the Twelve-Factor methodology. Here follows some actionable advice from the WhiteHat Security Addendum Checklist, which developers and ops engineers can follow during the SaaS build and operations stages ...

June 21, 2018

DevSecOps is quickly gaining support and traction, within and beyond information security teams. In fact, 70% of respondents believe their culture can embrace the change needed to fuse Security and DevOps, according to a new survey of 80 security professionals by Aqua Security ...

June 20, 2018

The larger the company size, the higher the proportion of low IT performers, according to the State of DevOps: Market Segmentation Report from Puppet, based on the 2017 State of DevOps Survey data ...

Share this