Harrison 
OpsMx announces a new approach to application security. Deployment firewall. This firewall is integrated into your CI/CD pipeline and enforces application security policies during application deployment, blocking releases if there are vulnerabilities or security issues.
According to OpsMx, recent application security efforts across the industry have focused on the application development process. The company recognizes that this is an important part of application security, but responsibilities are spread across distributed development teams with different toolsets and operating models, making it difficult to enforce security policies. There may be cases.
said Gopal Dommy, CEO and Founder of OpsMx. “Organizations know what they need to do for application security and release compliance, but are often stuck with siled data and distributed teams operating in systems of honor. Deployment firewalls combine rich datasets with good intentions to make security policies actionable.”
With the release of Deployment Firewall, enterprises now have a firewall that can evaluate applications against a variety of policies and block their release if they don’t meet all requirements. Qualifications used to determine whether a release should be performed include manifest files, vulnerability scans, artifact integrity, infrastructure readiness, release quality and performance, and operational management. Masu.
OpsMx provides a set of firewall rules that can be extended or customized by the customer.
These rules can also be used to check compliance with popular frameworks such as NIST 800, PCI, and HIPAA.
The tool also provides an option to simulate a deployment before it is ready to deploy, allowing you to proactively check application compliance.
Deployment Firewall is part of the OpsMx Deploy Shield product and can be added to existing Jenkins, Argo, and Spinnaker implementations. The company also plans to add support for GitHub Actions and GitLab in the future.
