Content you might like
Patch management: to reduce attack surface and avoid system misconfigurations39%
Malware and ransomware prevention: to protect endpoints from social engineering attacks59%
Malware and fileless malware detection and response: to protect against malicious software49%
Threat Hunting: to detect unknown threats that are acting or dormant in your environment and have bypassed the security controls33%
Not planning to change endpoint security strategy9%
Limited environment/Infrastructure resources32%
Inability to quickly identify the root cause of CI/CD pipeline failures45%
Lack of standardized CI/CD pipeline templates across the organization54%
Integrating security tools - inefficient security implementation leading to false positives38%
Poor communication across business and product teams/coordination challenges26%
Cost/resource management26%
Implementation of CI/CD into on-going projects and workflows22%
Internal resistance: training issues, culture, etc.14%
Inefficient implementation of CI/CD due to lack of expertise, poor training, etc.19%
Poorly written unit and acceptance testing9%
I definitely agree that, yes, security should be baked into DevOps, but if you have to put sec to the word to remind people, and to make that a cultural aspect. I think that's good as well.