SonicOS 7.1 Objects
- SonicOS 7.1 Action Objects
- About SonicOS
- Match Objects
- Zones
- How Zones Work
- Default Zones
- Security Types
- Allow Interface Trust
- Effect of Wireless Controller Modes
- Zones Overview
- The Zones Page
- Adding a New Zone
- Adding a New Zone in Policy Mode
- Adding a New Zone in Classic Mode
- Configuring a Zone for Guest Access
- Configuring a Zone for Open Authentication and Social Login
- Configuring the WLAN Zone
- Configuring the RADIUS Server
- Configuring DPI-SSL Granular Control per Zone
- Enabling Automatic Redirection to the User-Policy Page
- Cloning a Zone
- Editing a Zone
- Deleting Custom Zones
- Addresses
- Addresses Page
- About UUIDs for Address Objects and Groups
- Working with Dynamic Address Objects
- Services
- URI Lists
- Schedules
- Dynamic Group
- Email Addresses
- Match Objects
- Countries
- Applications
- Web Categories
- Websites
- Match Patterns
- Custom Match
- Profile Objects
- Endpoint Security
- Bandwidth
- QoS Marking
- Content Filter
- DHCP Option
- DNS Filtering
- Block Page
- Anti-Spyware
- Gateway Anti-Virus
- Log and Alerts
- Intrusion Prevention
- AWS
- Action Profiles
- Security Action Profile
- DoS Action Profile
- Action Objects
- App Rule Actions
- Content Filter Actions
- Object viewer
- SonicWall Support
Addresses
Address objects (AOs) allow for entities to be defined one time, and to be re-used in multiple referential instances throughout the SonicOS interface. While more effort is involved in creating an address object than in simply entering an IP address, address objects were implemented to complement the management scheme of SonicOS, providing the following characteristics:
-
Zone Association
When defined, host, MAC, and FQDN AOs require an explicit zone designation. In most areas of the interface (such as access rules (Classic Mode) or security policies (Policy Mode)) is only used referentially. The functional application are the contextually accurate populations of address object drop-down menus and the area of VPN access definitions assigned to users and groups. When AOs are used to define VPN access, the access rule auto-creation process refers to the AO’s zone to determine the correct intersection of VPN [zone] for rule placement. In other words, if the host AO, 192.168.168.200 , belonging to the LAN zone was added to VPN access for the Trusted Users user group, the auto-created access rule would be assigned to the VPN LAN zone.
-
Management and Handling
The versatile family of address objects types can be easily used throughout the SonicOS interface, allowing for handles (for example, when defining access rules (Classic Mode) or security policies (Policy Mode)) to be quickly defined and managed. The ability to simply add or remove members from address groups effectively enables modifications of referencing rules and policies without requiring direct manipulation.
-
Reusability
Objects only need to be defined once and can then be easily referenced as many times as needed.
For example, take an internal web server with an IP address of 67.115.118.80. Rather than repeatedly typing in the IP address when constructing access rules or NAT policies, you can create a single entity called My Web Server as a host address object with an IP address of 67.115.118.80. This address object, My Web Server, can then be easily and efficiently selected from a drop-down menu in any configuration screen that employs address objects as a defining criterion.
Was This Article Helpful?
Help us to improve our support portal