GitLab

vs

Saltstack

Cloud Native

GitLab and its CI/CD is Cloud Native, purpose built for the cloud model. GitLab can be easily deployed on Kubernetes and used to deploy your application to Kubernetes with support out of the box.

Kubernetes integration

Vulnerability Management

GitLab’s vulnerability management is about ensuring assets and applications are scanned for vulnerabilities. It also includes the processes to record, manage, and mitigate those vulnerabilities.

Vulnerability management helps identify meaningful sets of vulnerabilities, in both your assets and application code, that can be mitigated, managed, and acted upon by your whole team—not just the security organization. It also provides a unified interface to the systems teams are already using for managing results from the ~”devops::secure” stage so there is always a single source of truth and single place for managing security results.

Learn more about Vulnerability Management

Container Host Monitoring and Blocking

“With Container Host Monitoring, you can monitor running containers for malicious or unusual activity. This includes process starts, file changes, or opened network ports. You can also block or prevent these activities from occurring.”

Learn more about Container Host Monitoring and Blocking

Policy Management for Container Network Policies

“Policy Management for Container Network Policies provides an easy way to create, edit, delete, view, and manage Network Policies in the GitLab UI.”

Learn more about policy management for container Network Policies

License Compliance

Check that licenses of your dependencies are compatible with your application, and approve or deny them. Results are then shown in the Merge Request and in the Pipeline view.

Learn more about License Compliance

Configuration Modeling

CM modeling is the concept to consolidate the interactions between IT service assets, configuration items and infrastructure. Shows the interaction and relationship of services, infrastructure, and assets with each other, it will ease to find the root cause of an incident and problem.

Configuration Automation

Configure Management automation is used to make the server reach a desirable state, previously defined by provisioning scripts using a tool’s specific language and features ensuring that every system you’re responsible for is configured accurately and consistently.

Configure Monitoring

CM monitoring includes the process of recording and reporting configuration item descriptions (e.g., hardware, software, firmware, etc.) and all departures from the baseline during design and production. In the event of discovered problems, the verification of baseline configuration and approved modifications can be quickly determined.

Configure Governance

CM governance is a review that assesses compliance with established performance requirements, commercial and appropriate government standards, and functional, allocated, and product baselines. Configuration governance confirm that the system and subsystem configuration documentation complies with the functional and physical performance characteristics before acceptance into an architectural baseline.