📄️ Language Support
Lacework continues to expand its coverage of supported IaC languages. The following table outlines the current languages supported by the Lacework IaC Security Code Security App and associated CLI.
📄️ Configure IaC Security Settings
You can configure the following settings:
📄️ Modify IaC Security Policies
Click Policies on the left panel of the IaC Security Console to view the Policies page that displays the complete list of policies in the system.
📄️ Use Repositories
Click Repositories on the left panel of the Lacework IaC Security Console to display the Repositories page that lists the GitHub and GitLab repositories scanned.
📄️ Use Findings
Click a repository to view its Insights page and click View Findings at the bottom of the page to display the Assessments page.
📄️ View Violations
Click Violations on the left panel of the Lacework IaC Security Console to display the Violations page. This page provides the total number of violations in the main and master branch and lists each violation by its severity. It provides the policy summary and severity.
📄️ Enforce Checks Before Merging
After you set up IaC Security in your repository, you can mandate rules and checks to enable merging pull requests (GitHub/Bitbucket) or merge requests (GitLab).
📄️ Pull Request Build Status
IaC Security provides the following build status messages for pull requests.
📄️ Configure the Code Security App
IaC Security provides the ability to view policy violations without blocking Pull Request/Merge Requests (PR/MR) despite failed policy checks. This capability can be configured at the organization level, where it applies to all repositories, or at the repository level (through settings within the repository's .lacework/config.yml file, which take precedence over the organization configuration).