Thursday, September 19, 2024
Cloud Native Now
MENU
MENU
Home
Webinars
Upcoming
Calendar View
On-Demand
Podcasts
Cloud Native Now Podcast
Techstrong.tv Podcast
Techstrong.tv - Twitch
About
Sponsor
MENU
MENU
News
Latest News
News Releases
Cloud-Native Development
Cloud-Native Platforms
Cloud-Native Networking
Cloud-Native Security
Hot Topics
IBM Acquires Kubecost to Bring FinOps to Kubernetes Environments
Survey Surfaces Where Kubernetes Clusters Are Running Most
Tigera Adds Vulnerability Management Capabilities to Calico Platform
Komodor Adds Generative AI Tool to Simplify Kubernetes Management
Kubernetes in Multi-Cloud Environments
Sweet Security
Sweet Security Unfurls Cloud-Native Runtime Protection Platform
Sweet Security today launched a Cloud Runtime Security Suite platform for securing cloud-native application runtimes ...
Mike Vizard
|
August 9, 2023
|
cloud native security
,
Kubernetes clusters
,
software supply chain
,
Sweet Security
Application Security Check Up
Step
1
of
7
14%
Does someone in your organization write software?
(Required)
Yes
No
What portion of your cyber risk is Application Security (AppSec)? (Select one)
(Required)
We over-focus on AppSec
We focus on AppSec to match the risk
We under-focus on AppSec
What are the biggest challenges you face implementing a robust AppSec strategy? (Select all that apply)
Lack of budget
Insufficient skilled personnel
Complexity of integrating security into the development lifecycle
Resistance from development teams
Keeping up with evolving security threats
Lack of executive buy-in
Other (please specify)
Other
Which DevSecOps practices are widely used for actively developed projects (not legacy) (Select all that apply):
(Required)
Automated unit and functional tests for quality run in the pipeline with merge blocking
Automated application security testing (AST) in development and (SAST/IAST) runs in the pipeline
Automated AST tools to find vulnerabilities in the code you import (SCA) run in the pipeline
Merge blocking at current policy level for AST checks
Secrets management so no secrets stored in source code repositories
How do you assess and mitigate risk of For NON actively developed products (legacy) (Select all that apply):
In-production scans using DAST products like Qualys, Nessus, etc.
Periodic penetration testing
Periodic running of AST tools
Manual code reviews by security specialists
Use of third-party security assessment services
No assessment or mitigation effort is happening
How do you resolve the security issues found? (Select all that apply):
(Required)
Findings are manually triaged
Findings are communicated to engineering via mostly manual processes
Finding above a certain severity automatically populate engineering backlogs
Service level agreements (SLAs) are enforced based on severity
An exception process exists to allow the business to accept risk
The exception process is rarely used and must be renewed periodically
Which best describes security training for your developers? (Select all that apply)
(Required)
Monthly
Quarterly
Annually
As part of onboarding
Just-in-time via integration with AST tools when a vulnerability is found
No formal training provided
Δ
