Rapid7 (InsightAppSec cloud engines) IP ranges

Official Rapid7 (InsightAppSec cloud engines) ranges from the vendor's publication, split by purpose: appsec-engines. The ranges below render live from the signed slash0 feed.

purpose	direction	IPv4	IPv6
`rapid7/appsec-engines`	ingress	·	·

rapid7/appsec-engines

Direction: ingress. Ranges Rapid7 (InsightAppSec cloud engines) connects from (webhook delivery); use them in security group ingress rules on your receiving endpoints.

loading ranges from the feed…

Terraform

data "ipranges_ingress" "rapid7_appsec_engines" {
  service = "rapid7"
  purpose = "appsec-engines"
}

resource "aws_security_group_rule" "rapid7_appsec_engines" {
  type              = "ingress"
  from_port         = 443
  to_port           = 443
  protocol          = "tcp"
  cidr_blocks       = data.ipranges_ingress.rapid7_appsec_engines.ipv4_cidrs
  security_group_id = aws_security_group.app.id
}

keep rules current automatically

Terraform data sources refresh only when you run an apply. The hosted tier publishes the same data via AWS managed prefix lists (slash0.rapid7.appsec-engines.v4 and so on), shared into your account via AWS RAM: rules reference one pl-… id and update within a minute of a vendor change, with removals held through a 72 hour grace window. Request early access or read how it works.

provenance

Ranges come from Rapid7 (InsightAppSec cloud engines)'s official publication: https://docs.rapid7.com/insightappsec/allowlist-cloud-engine-ips/. Fetched sources:

https://docs.rapid7.com/insightappsec/allowlist-cloud-engine-ips/

Every publish is signed (ECDSA P-256 over the feed index, each service document hash-chained to it) and every range change is recorded in the changelog. Verification steps: security. Provider setup: quickstart.