Here are the highlights of the CNCF Cloud Native Security Technical Advisory Group (TAG) Survey. The article directly quotes the whitepaper as a block quote and adds commentary on how Accuknox can help address some of the challenges mentioned in the Microsurvey.

#1: Modernizing Security is really important

An overwhelming 85% of respondents indicated that modernizing security is very important to their organization’s cloud native deployment. Another 12% believe it is somewhat important, and 3% feel neutral. No one indicated that it is not important.

#2: Security policies is not fully automated and driven by trial and error

Accuknox automates the policy lifecycle:

Accuknox makes it easy for organizations to adopt fully open source based security components and automate the entire - policy auto-generation, policy auto approval cycle with the following user personas and user journeys:

#3: Security tools should be open source

82% of respondents said it’s important that the security systems they implement are built using open source software. No one indicated that they felt open source was too risky to trust, a sign that Linus’ Law is well understood

Accuknox's open-source solutions include:

Accuknox is built on open-souce first foundations and our contributions include:

#4 Key Challenges include

A lack of technical expertise (58%). This is not surprising as talent shortages have been reported in many other areas of software development. Also, cloud native security is a broad field, so the demand for security professional talent is high.
Trouble matching new methods and processes like DevOps and CI/CD with existing requirements, tools, or processes (51%). This is a well-known gap in the community – existing compliance frameworks have yet to catch up. While necessary, it is not particularly an exciting area, as we’ve seen with the general limits of automated compliance tooling (OSCAL being an exception).
Data Security (49%). Seeing this high-up on the list is actually a good thing. Organizations are considering shifting to a data-centric security model and might be positioning them- selves to begin looking into Zero Trust. It may become a more prolific area of focus in the coming years, so be sure to keep an eye out.
The complexity of building, deploying, and management (46%). This likely ties back to the lack of technical expertise. Like all technology revolutions, modern security requires a cultural shift, and many organizations are still figuring out how to do this. There is no “easy out” on cloud native journeys, and there certainly isn’t one for cloud native security. Each organization will need to learn and transform its approaches and processes while considering the existing documentation and papers available in this space, another where TAG Security contributes.

#5: The biggest concerns in Cloud Native Security

No secure-by-default guarantees or options (53%). This could be due to a lack of certifications or conformance with existing practices. Projects adhering to CII and adding a badge to their repositories could help to alleviate this concern around how projects were developed securely. However, it does not express a project as secure-by-default. There have been several nominations and ideas around the growing attestation of secure-defaults, but this is still nascent.
Visibility into systems, networks, and traffic (50%). While cloud native monitoring tools like Prometheus exist, they are primarily used for tracking performance. Tools like Falco will help, but it is still in the early stages of adoption.
Lack of information or understanding of threats to third-party software and publicly available code (39%). This is a problem with open source software in that no one is charged with providing this information. Foundations and groups need to work together to fill this need.
The health of the open source projects used to build cloud native (35%). This is another area where adding a CII badge or other security label could help to ensure conformance with secure development.
Lack of documentation explaining projects’ security (35%). This is often missed by projects that are not designed for security. The Security TAG encourages projects to complete a self-assessment and submit a pull request to their repo (for independent storage) to help identify gaps in documentation.

#6: Concerns about edge adoption include:

Misconfiguration (31%). This is due to a lack of documentation and testing for secure configurations.
Unpatched vulnerabilities (18%). Organizations should increase their release and update cadence to help address this.
Backdoors into the corporate network (15%). This underscored the importance of having identity and access management tools available and ensuring they are being utilized correctly.

#7: Cloud native projects addresing edge computing should have the following (security) capabilities

Detect and identify suspicious behavior (65%)
Secrets management (55%)
Data protection (55%)
Intrusion detection (53%)

#8: Vendor Lockin Concerns

Organizations would like to have multiple open source alternatives for the following proprietary technologies
1. Key Vault, Vault (59%)
2. Splunk, ELK (53%)
3. AWS Key Management Service (30%) 4. HSM replacement (23%)