reachability_result bool | reasoning string | effective_rules list | referenced_resources list | reachability_question string | terraform_source_code string |
|---|---|---|---|---|---|
true | The two subnets belong to the same VPC and share a route table, so the VPC local route provides a path between them. The attached security groups allow the requested TCP port in the outbound and inbound directions. The subnet ACLs are stateless, but each permits the request direction and the corresponding return-port r... | [
"Both subnets use aws_route_table.internal; the VPC's local route covers traffic between 10.20.1.0/24 and 10.20.2.0/24.",
"The app security group permits TCP egress on port 5432 to the db security group, and the db security group permits TCP ingress on port 5432 from the app security group.",
"The app network A... | [
"aws_vpc.core",
"aws_subnet.app",
"aws_subnet.db",
"aws_route_table.internal",
"aws_route_table_association.app",
"aws_route_table_association.db",
"aws_security_group.app",
"aws_security_group.db",
"aws_vpc_security_group_egress_rule.app_to_db",
"aws_vpc_security_group_ingress_rule.db_from_app",
... | At the network-policy layer, can the endpoint on aws_network_interface.app establish a TCP connection to aws_network_interface.db on port 5432? | resource "aws_vpc" "core" {
cidr_block = "10.20.0.0/16"
}
resource "aws_subnet" "app" {
vpc_id = aws_vpc.core.id
cidr_block = "10.20.1.0/24"
}
resource "aws_subnet" "db" {
vpc_id = aws_vpc.core.id
cidr_block = "10.20.2.0/24"
}
resource "aws_route_table" "internal" {
vpc_id = aws_vpc.core.id
}
re... |
true | The VPC CIDRs do not overlap, and the route tables contain routes in both directions through the accepted peering connection. The source and target security groups allow the requested TCP port for the respective subnet CIDRs. The stateless network ACLs also allow the outbound request, inbound delivery, and return traff... | [
"The source route table sends 10.50.0.0/16 traffic through aws_vpc_peering_connection.link, and the target route table sends 10.40.0.0/16 traffic through the same peering connection.",
"The source security group permits TCP egress on port 443 to 10.50.1.0/24, and the target security group permits TCP ingress on p... | [
"aws_vpc.source",
"aws_vpc.target",
"aws_subnet.source",
"aws_subnet.target",
"aws_vpc_peering_connection.link",
"aws_route_table.source",
"aws_route_table.target",
"aws_route_table_association.source",
"aws_route_table_association.target",
"aws_route.source_to_target",
"aws_route.target_to_sour... | At the network-policy layer, can the endpoint on aws_network_interface.source establish a TCP connection to aws_network_interface.target on port 443? | resource "aws_vpc" "source" {
cidr_block = "10.40.0.0/16"
}
resource "aws_vpc" "target" {
cidr_block = "10.50.0.0/16"
}
resource "aws_subnet" "source" {
vpc_id = aws_vpc.source.id
cidr_block = "10.40.1.0/24"
}
resource "aws_subnet" "target" {
vpc_id = aws_vpc.target.id
cidr_block = "10.50.1.0/24"... |
false | The VPC local route provides a path between the two associated subnets, and both security groups permit TCP port 8443 for the specified subnet CIDRs. However, network ACLs are stateless and the api subnet's inbound rule 100 explicitly denies this source CIDR and destination port. Because that deny is evaluated before r... | [
"Both subnets use aws_route_table.private; the VPC's local route covers traffic between 10.30.1.0/24 and 10.30.2.0/24.",
"The frontend security group permits TCP egress on port 8443 to 10.30.2.0/24, and the api security group permits TCP ingress on port 8443 from 10.30.1.0/24.",
"The frontend network ACL permit... | [
"aws_vpc.service",
"aws_subnet.frontend",
"aws_subnet.api",
"aws_route_table.private",
"aws_route_table_association.frontend",
"aws_route_table_association.api",
"aws_security_group.frontend",
"aws_security_group.api",
"aws_vpc_security_group_egress_rule.frontend_to_api",
"aws_vpc_security_group_i... | At the network-policy layer, can the endpoint on aws_network_interface.frontend establish a TCP connection to aws_network_interface.api on port 8443? | resource "aws_vpc" "service" {
cidr_block = "10.30.0.0/16"
}
resource "aws_subnet" "frontend" {
vpc_id = aws_vpc.service.id
cidr_block = "10.30.1.0/24"
}
resource "aws_subnet" "api" {
vpc_id = aws_vpc.service.id
cidr_block = "10.30.2.0/24"
}
resource "aws_route_table" "private" {
vpc_id = aws_vpc... |
Terraform Network Segmentation Reachability Reasoning Dataset
This dataset includes Terraform and other infrastructure-as-code configurations for cloud networks, security groups, network ACLs, routes, and their references, paired with supervised questions about reachability between specified resources. Examples cover reachability decisions, identification of applicable rules, and explanations of the results, helping models understand cross-resource references and network rule semantics. It is designed for supervised fine-tuning and evaluation of models for network segmentation analysis, code understanding, and reasoning.
Technical Specifications
| Field | Type | Description |
|---|---|---|
| reasoning | string | A concise explanation of how resource references and network rule semantics determine the reachability result. |
| effective_rules | array | The security group, network ACL, and route rules that determine the reachability result. |
| reachability_result | boolean | Indicates whether the queried source and destination resources can reach each other under the configured rules. |
| referenced_resources | array | Terraform resources and cross-resource references relevant to the reachability question. |
| reachability_question | string | A question about whether specified resources can communicate and which network rules apply. |
| terraform_source_code | string | Terraform configuration code containing network, security group, network ACL, and route resources, along with their references. |
Compliance Statement
| Authorization Type | CC-BY-NC-SA 4.0 (Attribution–NonCommercial–ShareAlike) |
| Commercial Use | Requires exclusive subscription or authorization contract (monthly or per-invocation charging) |
| Privacy and Anonymization | No PII, no real company names, simulated scenarios follow industry standards |
| Compliance System | Compliant with China's Data Security Law / EU GDPR / supports enterprise data access logs |
Source & Contact
- Downloads last month
- -