Why scope checks should parse targets into networks instead of comparing strings
On authorized penetration tests, signed scopes are typically short lists of CIDR blocks, while the targets testers type are often informal, such as copied dash ranges, wildcards, or stale hostnames. String comparisons or notes in a report can let these out-of-scope inputs slip through. The author proposes a standard-library Python check that stores scope only as CIDRs, defaults to private address space, and parses every target into a network before comparing it. Ambiguous or unparseable inputs are denied, and the check runs at every action so hosts added mid-engagement cannot bypass it. The approach does not determine what a client actually authorized, and hostname and IPv6 range handling remain open questions.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in