Product logo
DocsBlogPricing

@turbot/aws-vpc-security

Version
5.9.8
Released On
Apr 19, 2024
Depends On

Resource Types

Control Types

Policy Types

Release Notes

5.9.8 (2024-04-19)

Bug fixes

  • The AWS > VPC > Flow Log > Configured control would sometimes go into an error state for flow logs created via the AWS console, even though they were correctly claimed by a Guardrails stack. This is now fixed.

5.9.7 (2024-03-15)

Bug fixes

  • The AWS > VPC > VPC > Stack control failed to claim security group rules correctly if the protocol for such rules was set to All or TCP in the stack's source policy. This issue has been fixed, and the control will now claim such rules correctly.

5.9.6 (2024-03-11)

Bug fixes

  • In the previous version, we fixed an issue with the AWS > VPC > VPC > Stack control that prevented it from recognizing security group rules with the port range set to 0 correctly. However, the control still failed to claim existing security group rules available in Guardrails CMDB, due to an inadvertent bug introduced in v5.9.2. This issue has now been fixed, and the control will correctly claim existing security group rules.
  • Guardrails failed to filter out real-time events for resource types if their parent resource types' CMDB policy was set to Enforce: Disabled. This is now fixed.

5.9.5 (2024-03-06)

Bug fixes

  • The AWS > VPC > Security Group > CMDB control would sometimes go into an error state for security groups shared from other AWS accounts. We will now exclude shared security groups and only upsert security groups that belong to the owner account.
  • The AWS > VPC > VPC > Stack control would sometimes go into an error state after creating security group rules with the port range set to 0. This occurred because the control failed to recognize the existing rule in Guardrails CMDB and attempted to create a new rule instead. This issue has been fixed, and the stack control will now work correctly as expected.

5.9.4 (2024-02-22)

Bug fixes

  • The AWS > VPC > VPC > Stack control would sometimes fail to claim existing Flow Logs in Guardrails CMDB. This is now fixed.

5.9.3 (2023-09-18)

Bug fixes

  • The AWS > VPC > Security Group > CMDB control would sometimes go into an error state if the TE version installed on the workspace was 5.42.1 or lower. This is fixed and the control will now work as expected.

5.9.2 (2023-09-15)

Bug fixes

  • Guardrails stack controls would fail to claim any existing Security Group if the Security Group was available in Guardrails CMDB and the stack's Source policy included the Terraform plan for the Security Group. This is fixed and stack control will now be able to claim existing Security Groups correctly. Please note that this fix will only work for workspaces on TE v5.42.2 or higher.
  • Guardrails stack controls would sometimes fail to update Security Groups and Security Group Rules if the Terraform plan in the stack's source policy included changes to attributes which force replaced the resource. This is fixed and the stack controls will now update such resources correctly, as expected. Please note that this fix will only work for workspaces on TE v5.42.2 or higher.

5.9.1 (2023-07-03)

Bug fixes

  • The AWS > VPC > Security Group > Active control will now run every 24 hours to evaluate attachments on the Security Group more consistently than before.
  • We've updated the runtime of the lambda functions to Node 18. You wouldn't notice any difference and things will continue to work smoothly and consistently as before.

5.9.0 (2023-06-15)

What's new?

  • Resource's metadata will now also include createdBy details in Turbot CMDB.

Bug fixes

  • We've added new Turbot AKAs for AWS > VPC resource types that match their individual unique identifiers. E.g. FlowLogId will now also be a Turbot AKA for AWS > VPC > Flow Log, NetworkAclId for AWS > VPC > Network ACL etc.. Querying such resources in Turbot will now be easier than before.

Action Types

  • AWS > VPC > Flow Log > Set Tags
  • AWS > VPC > Flow Log > Skip alarm for Active control
  • AWS > VPC > Flow Log > Skip alarm for Active control [90 days]
  • AWS > VPC > Flow Log > Skip alarm for Approved control
  • AWS > VPC > Flow Log > Skip alarm for Approved control [90 days]
  • AWS > VPC > Flow Log > Skip alarm for Tags control
  • AWS > VPC > Flow Log > Skip alarm for Tags control [90 days]
  • AWS > VPC > Network ACL > Set Tags
  • AWS > VPC > Network ACL > Skip alarm for Active control
  • AWS > VPC > Network ACL > Skip alarm for Active control [90 days]
  • AWS > VPC > Network ACL > Skip alarm for Approved control
  • AWS > VPC > Network ACL > Skip alarm for Approved control [90 days]
  • AWS > VPC > Network ACL > Skip alarm for Tags control
  • AWS > VPC > Network ACL > Skip alarm for Tags control [90 days]
  • AWS > VPC > Security Group > Set Tags
  • AWS > VPC > Security Group > Skip alarm for Active control
  • AWS > VPC > Security Group > Skip alarm for Active control [90 days]
  • AWS > VPC > Security Group > Skip alarm for Approved control
  • AWS > VPC > Security Group > Skip alarm for Approved control [90 days]
  • AWS > VPC > Security Group > Skip alarm for Tags control
  • AWS > VPC > Security Group > Skip alarm for Tags control [90 days]
  • AWS > VPC > Security Group Rule > Set Tags
  • AWS > VPC > Security Group Rule > Skip alarm for Tags control
  • AWS > VPC > Security Group Rule > Skip alarm for Tags control [90 days]

5.8.0 (2022-02-16)

What's new?

  • Users can now create their own custom checks against resource attributes in the Approved control using the Approved > Custom policy. These custom checks would be a part of the evaluation of the Approved control. Custom messages can also be added which are then displayed in the control details table. See Custom Checks for more information.

Bug fixes

  • We've improved the process of deleting resources from Turbot if their CMDB policy was set to Enforce: Disabled. The CMDB controls will now not look to resolve credentials via Turbot's IAM role while deleting resources from Turbot. This will allow the CMDB controls to process resource deletions from Turbot more reliably than before.

Policy Types

  • AWS > VPC > Flow Log > Approved > Custom
  • AWS > VPC > Network ACL > Approved > Custom
  • AWS > VPC > Security Group > Approved > Custom

5.7.0 (2022-01-13)

What's new?

  • Security Group Rules now include SecurityGroupRuleId in their CMDB data. You can now also check and/or set tags on Security Group Rules. To get started, set the AWS > VPC > Security Group Rule> Tags and AWS > VPC > Security Group Rule> Tags > Template policies.

Control Types

  • AWS > VPC > Security Group Rule > Tags

Policy Types

  • AWS > VPC > Security Group Rule > Tags
  • AWS > VPC > Security Group Rule > Tags > Template

Action Types

  • AWS > VPC > Security Group Rule > Router
  • AWS > VPC > Security Group Rule > Update Tags

5.6.0 (2021-07-20)

What's new?

  • We've added support for ec2:ModifySecurityGroupRules event and the AWS > VPC > Security Group > CMDB and AWS > VPC > Security Group Rule > CMDB controls will now be updated automatically if an ec2:ModifySecurityGroupRules event is raised in Turbot.
  • We've improved the details tables in the Tags controls to be more helpful, especially when a resource's tags are not set correctly as expected. Previously, to understand why the Tags controls were in an Alarm state, you would need to find and read the control's process logs. This felt like too much work for a simple task, so now these details are visible directly from the control page.

5.5.1 (2021-05-21)

Bug fixes

  • We’ve made a few improvements in the GraphQL queries for various controls, policies, and actions. You won’t notice any difference, but things should run lighter and quicker than before.

5.5.0 (2021-04-02)

Bug fixes

  • We've improved our event handling configuration and now filter which AWS events Turbot listens for based on resources' CMDB policies. If a resource's CMDB policy is not set to Enforce: Enabled, the EventBridge rules will be configured to not send any events for that resource. This will greatly reduce the number of unnecessary events that Turbot listens for and handles today.

Policy Types

  • AWS > Turbot > Event Handlers > Events > Rules > Custom Event Patterns > @turbot/aws-vpc-security

5.4.0 (2021-02-24)

What's new?

  • We've improved the state reasons and details tables in various Approved and Active controls to be more helpful, especially when a resource is unapproved or inactive. Previously, to understand why one of these controls is in Alarm state, you would need to find and read the control's process logs. This felt like too much work for a simple task, so now these details are visible directly from the control page.

5.3.4 (2021-01-25)

Bug fixes

  • We've updated the examples for the AWS > VPC > Security Group > Ingress Rules > Approved > Rules and AWS > VPC > Security Group > Ingress Rules > Approved > Rules policies to contain more clear rules for checking ports.

5.3.3 (2021-01-08)

Bug fixes

  • We've improved the real-time event handling for tag events that update multiple resources at a time and now all resources in a tag event will be updated in CMDB consistently.

5.3.2 (2020-12-17)

Security

  • Since v5.0.0, the AWS > VPC > Security Group > Egress Rules > Approved and AWS > VPC > Security Group > Ingress Rules > Approved controls would sometimes not mark security group rules with a port range containing prohibited ports as unapproved. This scenario would specifically occur when a security group rule's port range contained prohibited and allowed ports, resulting in the control incorrectly passing the security group rule as approved. Please note that if a security group rule's port range was limited to a single port, and that port was prohibited, the security group rule would correctly be marked unapproved.

    We have fixed how the controls evaluate security group rules and now any security group rules containing any prohibited ports will be marked unapproved correctly.

    We recommend updating this mod to the latest version to ensure these fixes are installed.

Bug fixes

  • Controls run faster now when in the tbd and skipped states thanks to the new Turbot Precheck feature (not to be confused with TSA PreCheck). With Turbot Precheck, controls avoid running GraphQL input queries when in tbd and skipped, resulting in faster and lighter control runs.

5.3.1 (2020-12-08)

Bug fixes

  • We've optimized the GraphQL queries for various controls when they're in the tbd and skipped states. You won't notice any difference but they should run a lot lighter now.

5.3.0 (2020-11-19)

What's new?

  • The AWS > VPC > Security Group > Active control can now check if a security group is attached to any resource or not. To enable this active check, please set the AWS > VPC > Security Group > Active > Attached policy.

Policy Types

  • AWS > VPC > Security Group > Active > Attached

5.2.7 (2020-11-06)

Bug fixes

  • AWS > VPC > Security Group Rule > Discovery control would end up in an error state if we tried upserting a large number of security group rules. This is now fixed and the AWS > VPC > Security Group Rule > Discovery control should now work smoothly, as expected.

5.2.6 (2020-10-16)

Bug fixes

  • We've made some improvements to our real-time event handling to monitor any changes made to the description of a security group's inbound and outbound rules.

5.2.5 (2020-09-24)

Bug fixes

  • We've made some improvements to our real-time event handling that reduces the risk of creating resources in CMDB with malformed AKAs. There's no noticeable difference, but things should run more reliably now.

5.2.4 (2020-09-17)

Bug fixes

  • We've made some improvements to our real-time event handling that reduces the risk of creating resources in CMDB with malformed AKAs. There's no noticeable difference, but things should run more reliably now.

5.2.3 (2020-08-17)

Bug fixes

  • Improvements were made to the GraphQL input queries for AWS > VPC > Flow Log > Discovery to make sure that they run less frequently over time, and still upsert flow logs under the correct resource parent(VPC, subnet or ENI).

5.2.2 (2020-08-07)

Bug fixes

  • Whenever the AWS > VPC > Stack control tried to claim a security group rule that allowed access over all ports, it would fail to do so because the required properties ToPort and FromPort were not returned by AWS APIs. This issue has been fixed and now we assign values of 0 and 65535 to FromPort and ToPort respectively when these properties are not returned.

5.2.1 (2020-08-03)

Bug fixes

  • The AWS > VPC > Flow Log > Discovery control would always upsert a flow log under its region, instead of under its actual resource parent (VPC, subnet, or network interface). This has now been fixed.

5.2.0 (2020-08-03)

Control Types

  • AWS > VPC > Flow Log > Tags

Policy Types

  • AWS > VPC > Flow Log > Tags
  • AWS > VPC > Flow Log > Tags > Template

Action Types

  • AWS > VPC > Flow Log > Update Tags

5.1.2 (2020-07-08)

Bug fixes

  • Sometimes when updating CMDB for resources with tags that have empty string values, e.g., [{Key: "Empty", Value: ""}, {Key: "Turbot is great", Value: "true"}], we would not store all of the tags correctly. This has been fixed and now all tags are accounted for.

5.1.1 (2020-06-11)

Bug fixes

  • Improved structure of logging messages in AWS > VPC > Security Group > Ingress Rules > Approved and AWS > VPC > Security Group > Egress Rules > Approved controls that would sometimes cause the controls to move to error state.

5.1.0 (2020-05-26)

Bug fixes

  • The AWS > VPC > Security Group > Ingress Rules Approved and AWS > VPC > Security Group > Egress Rules Approved controls will now remain in invalid state if the AWS > VPC > Security Group > CMDB policy is set to skip to let users know the CMDB is not current and the rules cannot be checked accurately.
  • Links to documentation in the descriptions for several controls and policies were broken. These links have now been fixed.

Resource Types

  • AWS > VPC > Security Group Rule

Control Types

  • AWS > VPC > Security Group Rule > CMDB
  • AWS > VPC > Security Group Rule > Configured
  • AWS > VPC > Security Group Rule > Discovery

Policy Types

  • AWS > VPC > Security Group Rule > CMDB
  • AWS > VPC > Security Group Rule > Configured
  • AWS > VPC > Security Group Rule > Configured > Claim Precedence
  • AWS > VPC > Security Group Rule > Configured > Source

5.0.4 (2020-05-06)

Policy Types

Renamed

  • AWS > VPC > Flow Log > Configured > Precedence to AWS > VPC > Flow Log > Configured > Claim Precedence
  • AWS > VPC > Network ACL > Configured > Precedence to AWS > VPC > Network ACL > Configured > Claim Precedence
  • AWS > VPC > Security Group > Configured > Precedence to AWS > VPC > Security Group > Configured > Claim Precedence