Record what each rule allows

For each rule, record source, destination, service, purpose, owner and expiry date. Include cloud security groups, network firewalls and host-level rules.

Look for broad sources, any-to-any rules and access created for temporary troubleshooting. Confirm the application owner still needs the connection.

Change rules with a rollback plan

Test a proposed removal in a safe window. Keep a rollback path for a business-critical service and notify the owner before a change.

Use narrow source and destination ranges. Separate administrative access from public application traffic where the design allows it.

Review activity and remove stale entries

Use traffic logs to check whether a rule is used, but do not treat a quiet period as proof that it is unnecessary. Ask the service owner and confirm dependencies.

Set a recurring review date and remove temporary rules when work ends. Record the decision and who approved it.