2020 Platform Releases
Recommendations —Support for the following new recommendations:
LW_AWS_NETWORKING_37 —Redshift Cluster should not be Publicly Accessible
LW_AWS_NETWORKING_38 —ELB Security Group should have Outbound Rules attached to it
LW_AWS_NETWORKING_39 —ELB should not use insecure Cipher(s)
LW_AWS_NETWORKING_40 —EC2 instance should be deployed in EC2-VPC platform
LW_AWS_NETWORKING_41 —CloudFront Origin Protocol Policy should use https-only
LW_AWS_NETWORKING_42 —CloudFront Origin SSL Protocols should not use insecure Cipher(s)
LW_AWS_NETWORKING_43 —Security group should not allow inbound traffic from all to all ICMP
LW_AWS_NETWORKING_44 —ELB should have VPC ingress security group
LW_AWS_NETWORKING_45 —ELB should have valid and secure security group
LW_AWS_GENERAL_SECURITY_5 —Ensure Redshift Cluster is encrypted
LW_AWS_GENERAL_SECURITY_6 —Ensure no server certificate has been uploaded before Heartbleed vulnerability
LW_AWS_GENERAL_SECURITY_7 —Ensure ELB has latest Secure Cipher policies Configured for Session Encryption
LW_AWS_GENERAL_SECURITY_8 —Ensure ELB is not affected by POODLE Vulnerability (CVE-2014-3566)
Populate Fields in Jira Outgoing Integration —Support for configuring the Jira Outgoing Integration to populate Jira fields with values from a custom template when the Jira Integration creates new Jira issues. For more information, see https://support.lacework.com/hc/en-us/articles/360023236593-JIRA .
Group Events by Resources in the Jira Outgoing Integration —Support for configuring the Jira Outgoing Integration to create multiple Jira issues when multiple resources are generating the same event. For example, if three different S3 resources are generating the same event, three Jira open issues are created. For more information, see https://support.lacework.com/hc/en-us/articles/360023236593-JIRA .
Polygraph search enhancements —The polygraph search now supports additional operators: - AND, OR. For more information, see https://support.lacework.com/hc/en-us/articles/360034692034 .