@turbot/aws-vpc-security
Recommended Version
@turbot/turbot ^5.22.0
@turbot/turbot-iam ^5.1.0
@turbot/aws-iam ^5.1.0
@turbot/aws-ec2 ^5.0.0
@turbot/aws-kms ^5.0.0
@turbot/aws-vpc-core ^5.0.0
Resource Types
- AWS > VPC > Flow Log
- AWS > VPC > Network ACL
- AWS > VPC > Security Group
- AWS > VPC > Security Group Rule
Control Types
- AWS > VPC > Flow Log > Active
- AWS > VPC > Flow Log > Approved
- AWS > VPC > Flow Log > CMDB
- AWS > VPC > Flow Log > Configured
- AWS > VPC > Flow Log > Discovery
- AWS > VPC > Flow Log > Tags
- AWS > VPC > Flow Log > Usage
- AWS > VPC > Network ACL > Active
- AWS > VPC > Network ACL > Approved
- AWS > VPC > Network ACL > CMDB
- AWS > VPC > Network ACL > Configured
- AWS > VPC > Network ACL > Discovery
- AWS > VPC > Network ACL > Tags
- AWS > VPC > Network ACL > Usage
- AWS > VPC > Security Group > Active
- AWS > VPC > Security Group > Approved
- AWS > VPC > Security Group > CMDB
- AWS > VPC > Security Group > Configured
- AWS > VPC > Security Group > Discovery
- AWS > VPC > Security Group > Egress Rules
- AWS > VPC > Security Group > Egress Rules > Approved
- AWS > VPC > Security Group > Ingress Rules
- AWS > VPC > Security Group > Ingress Rules > Approved
- AWS > VPC > Security Group > Tags
- AWS > VPC > Security Group > Usage
- AWS > VPC > Security Group Rule > CMDB
- AWS > VPC > Security Group Rule > Configured
- AWS > VPC > Security Group Rule > Discovery
- AWS > VPC > Security Group Rule > Tags
Policy Types
- AWS > Turbot > Event Handlers > Events > Rules > Custom Event Patterns > @turbot/aws-vpc-security
- AWS > VPC > Flow Log > Active
- AWS > VPC > Flow Log > Active > Age
- AWS > VPC > Flow Log > Active > Budget
- AWS > VPC > Flow Log > Active > Last Modified
- AWS > VPC > Flow Log > Approved
- AWS > VPC > Flow Log > Approved > Budget
- AWS > VPC > Flow Log > Approved > Custom
- AWS > VPC > Flow Log > Approved > Regions
- AWS > VPC > Flow Log > Approved > Usage
- AWS > VPC > Flow Log > CMDB
- AWS > VPC > Flow Log > Configured
- AWS > VPC > Flow Log > Configured > Claim Precedence
- AWS > VPC > Flow Log > Configured > Source
- AWS > VPC > Flow Log > Regions
- AWS > VPC > Flow Log > Tags
- AWS > VPC > Flow Log > Tags > Template
- AWS > VPC > Flow Log > Usage
- AWS > VPC > Flow Log > Usage > Limit
- AWS > VPC > Network ACL > Active
- AWS > VPC > Network ACL > Active > Age
- AWS > VPC > Network ACL > Active > Last Modified
- AWS > VPC > Network ACL > Approved
- AWS > VPC > Network ACL > Approved > Custom
- AWS > VPC > Network ACL > Approved > Regions
- AWS > VPC > Network ACL > Approved > Usage
- AWS > VPC > Network ACL > CMDB
- AWS > VPC > Network ACL > Configured
- AWS > VPC > Network ACL > Configured > Claim Precedence
- AWS > VPC > Network ACL > Configured > Source
- AWS > VPC > Network ACL > Regions
- AWS > VPC > Network ACL > Tags
- AWS > VPC > Network ACL > Tags > Template
- AWS > VPC > Network ACL > Usage
- AWS > VPC > Network ACL > Usage > Limit
- AWS > VPC > Security Group > Active
- AWS > VPC > Security Group > Active > Age
- AWS > VPC > Security Group > Active > Attached
- AWS > VPC > Security Group > Active > Last Modified
- AWS > VPC > Security Group > Approved
- AWS > VPC > Security Group > Approved > Custom
- AWS > VPC > Security Group > Approved > Regions
- AWS > VPC > Security Group > Approved > Usage
- AWS > VPC > Security Group > CMDB
- AWS > VPC > Security Group > Configured
- AWS > VPC > Security Group > Configured > Claim Precedence
- AWS > VPC > Security Group > Configured > Source
- AWS > VPC > Security Group > Egress Rules
- AWS > VPC > Security Group > Egress Rules > Approved
- AWS > VPC > Security Group > Egress Rules > Approved > CIDR Ranges
- AWS > VPC > Security Group > Egress Rules > Approved > Compiled Rules
- AWS > VPC > Security Group > Egress Rules > Approved > Maximum Port Range
- AWS > VPC > Security Group > Egress Rules > Approved > Minimum Bitmask
- AWS > VPC > Security Group > Egress Rules > Approved > Prohibited Ports
- AWS > VPC > Security Group > Egress Rules > Approved > Rules
- AWS > VPC > Security Group > Ingress Rules
- AWS > VPC > Security Group > Ingress Rules > Approved
- AWS > VPC > Security Group > Ingress Rules > Approved > CIDR Ranges
- AWS > VPC > Security Group > Ingress Rules > Approved > Compiled Rules
- AWS > VPC > Security Group > Ingress Rules > Approved > Maximum Port Range
- AWS > VPC > Security Group > Ingress Rules > Approved > Minimum Bitmask
- AWS > VPC > Security Group > Ingress Rules > Approved > Prohibited Ports
- AWS > VPC > Security Group > Ingress Rules > Approved > Rules
- AWS > VPC > Security Group > Regions
- AWS > VPC > Security Group > Tags
- AWS > VPC > Security Group > Tags > Template
- AWS > VPC > Security Group > Usage
- AWS > VPC > Security Group > Usage > Limit
- 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
- AWS > VPC > Security Group Rule > Tags
- AWS > VPC > Security Group Rule > Tags > Template
Release Notes
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 forAWS > VPC > Flow Log
,NetworkAclId
forAWS > VPC > Network ACL
etc.. Querying such resources in Turbot will now be easier than before.
Action Types
Added
- 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
Added
- 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 theAWS > VPC > Security Group Rule> Tags
andAWS > VPC > Security Group Rule> Tags > Template
policies.
Control Types
Added
- AWS > VPC > Security Group Rule > Tags
Policy Types
Added
- AWS > VPC > Security Group Rule > Tags
- AWS > VPC > Security Group Rule > Tags > Template
Action Types
Added
- 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 theAWS > VPC > Security Group > CMDB
andAWS > VPC > Security Group Rule > CMDB
controls will now be updated automatically if anec2: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
Added
- 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
andAWS > 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
andAWS > 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
andskipped
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 intbd
andskipped
, 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
andskipped
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 theAWS > VPC > Security Group > Active > Attached
policy.
Policy Types
Added
- 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 theAWS > 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 propertiesToPort
andFromPort
were not returned by AWS APIs. This issue has been fixed and now we assign values of0
and65535
toFromPort
andToPort
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
Added
- AWS > VPC > Flow Log > Tags
Policy Types
Added
- AWS > VPC > Flow Log > Tags
- AWS > VPC > Flow Log > Tags > Template
Action Types
Added
- 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
andAWS > 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
andAWS > VPC > Security Group > Egress Rules Approved
controls will now remain in invalid state if theAWS > 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
Added
- AWS > VPC > Security Group Rule
Control Types
Added
- AWS > VPC > Security Group Rule > CMDB
- AWS > VPC > Security Group Rule > Configured
- AWS > VPC > Security Group Rule > Discovery
Policy Types
Added
- 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