An enterprise address and naming plan should make each security device identifiable across locations and future growth. Coordinate the plan with customer IT before connecting inherited sites or copying a local configuration.
Part of Enterprise Security Network Reference Design.
Set address and naming conventions
Define site and device identifiers, address allocation responsibility, naming conventions, required network services, and the system of record. Reserve capacity for expansion and distinguish stable identifiers from names that may change with building use. Record the relationship between a device, switch port, location, and application label.
Handle acquisitions and conflicting records
Acquisitions, overlapping private addresses, renamed buildings, replacement equipment, and temporary networks can create ambiguous records. Document exceptions and the approved transition plan. Avoid embedding sensitive technical details into public names or broadly accessible documents; keep operational records within authorized systems.
Check labels through to the application
Check a representative set of devices from the physical label through network records and the security application. Verify name resolution, time configuration, site uniqueness, and the process for replacement. Test that a newly added location follows the scheme without conflicting with existing records.
Related planning resources
Let’s talk about your next step
Tell us what you want to improve and which locations are involved. We can help you work through the questions, check what your systems support, and define a practical project scope.