A security-list rule states a permitted traffic boundary. Its protocol, source or destination, port range and statefulness all matter. An approved support range should not become the whole internet merely because a broader rule makes a quick test easier.
The original operations tasks store explicit rule arrays in a local security list. They distinguish creation from association: the intended subnet or VNIC path still needs the relevant controls reviewed. The simulator doesn't evaluate live packets or reproduce every interaction between security lists, network security groups and routing. Treat the saved rule as reviewable intent. A production check must exercise the actual caller, route, target listener and required return path before reporting connectivity.
Preserve the requested source, protocol, destination port and statefulness.