UBIKA WAAP Container by UBIKA is a future product designed to help deliver cloud-native applications that integrate security into their own code. It easily integrates into the existing DevOps environment, implementing directly into the developers' CI/CD pipeline with existing tools like Gitlab, Jenkins, etc. UBIKA WAAP Container uses the same formats (like YAML, GO like), the same form factor (Docker images), and the same languages and concepts, facilitating management, reducing total cost of ownership, and preventing developers from having to learn new things. It will increase ROI by automatically adapting to application traffic and will be deployed close to the application in inline or sidecar mode. This will allow users to scale up or down traffic simultaneously with the application, using their orchestrator, in Kubernetes or Docker clusters. It will automatically adapt to the application's load, reducing resource costs and increasing return on investment (ROI). UBIKA WAAP Container improves security by enhancing context description. The solution and context description (such as persistence type, programming language, server operating system, data format) will be integrated into a configuration file close to the application code. Security will remain up to date, aligning with the application version. Security policies can be automatically adapted by invoking relevant security engines, thus improving overall security with fewer false positives. It simplifies the approach with proactive engines and a positive security model. Designed with API priority, the solution will apply OpenAPI files to secure the entire lifecycle. It will activate security engines based on 20 years of expertise, rate limiting, and bot mitigation capabilities to address the OWASP Top 10, zero-day attacks, DoS, and threats like credential stuffing that do not exploit CVEs. UBIKA WAAP Container contributes to the construction of Cloud Workload Protection Platform (CWPP) and includes features like SAST and DAST. It addresses challenges of modern cloud-native applications, considering the OWASP Top 10 and other important attacks like credential stuffing. It uses context description and positive security models to reduce false positives and reinforces responsibility by creating security policy versions. It uses security engines based on 20 years of proven expertise and smart scaling to save resource costs by automatically reducing or scaling down. It easily updates by leveraging microservices and meets the needs of modern cloud-native applications.