Device registration is how SC//AcuVigil™ identifies a device, ties it to the correct firewall policy, and makes sure the device only gets the access it is supposed to have.
In SC//AcuVigil, devices connected to the LAN of an edge security device (ESD) generally do not receive normal network access until they are registered and assigned a policy. A device may be plugged in and live on a VLAN, but it still won't have the right internet, VPN, or cross-network access until registration is completed correctly.
This differs from many traditional firewall environments, where broad rules are applied mainly at the VLAN level. In SC//AcuVigil, access is controlled more tightly at the device level. The registration record tells the platform what the device is, where it belongs, what IP address it should use, what policy should control its traffic, and how seriously to alert if it has a problem.
Why it matters
Device registration supports both security and operations.
Security. Policies in SC//AcuVigil act as per-device firewall rules. They define allowed communications such as outbound internet access, access to local networks, and VPN access. If traffic is not explicitly allowed by the policy, it is blocked. That deny-by-default approach is one reason registration matters: a device should not simply be connected and trusted. It should be identified, matched to a business purpose, and given only the access it needs.
PCI-DSS. For PCI-DSS, the practical message is that you must know what is on your network and restrict access appropriately, especially around payment-related environments. Registration creates an auditable inventory of expected devices and ties each one to a controlled policy. The SC//AcuVigil dashboard supports this with reports such as Unregistered Devices, Unrestricted Devices, and Device Exceptions, which help you detect inventory gaps and authorization problems.
In short, registration helps answer these questions:
- Is this device supposed to be here?
- Is it on the correct network segment?
- Does it have only the access it needs?
- Can you report on unregistered or overly permissive devices?
How policies fit in
A registration without the right policy is incomplete. The policy determines what communications are allowed, and in SC//AcuVigil policies are applied per device, not just per VLAN. Choosing the correct policy is one of the most important parts of registration.
Five default policies are present on every site. Choose by what the device needs to reach:
| Policy | Choose it for |
|---|---|
| Local | Devices that only need to reach other devices at the site. |
| VPN | Devices that need to reach systems at another location over the site's VPN tunnels. |
| InternetAccess | Devices that need outbound internet access only. This is a permissive policy; see the warning below. |
| Monitor | Devices you want registered but without any network access. |
| Unrestricted | Rarely. Gives open VPN and internet access. Only users with the Admin role can assign it. |
For each policy's description as shown in the dashboard, see Default policies.
Note: Monitor registers a device without giving it any network access. The policy sets no firewall rules for the device, and the ESD drops any traffic that isn't explicitly allowed, so the device's traffic stays blocked. Use Monitor when a device should be known and registered, so it no longer shows as unregistered and doesn't raise the site's status, but shouldn't have network access. Despite its description in the dashboard ("not managed by the gateway"), Monitor doesn't open the device's traffic. |
Warning: Unrestricted and InternetAccess are permissive policies. They grant more access than is normally appropriate and can introduce unnecessary risk. They may resolve a connectivity issue quickly, but they should not be the default fix for troubleshooting. Apply them only when there is a specific, approved need. Your company may also have custom policies that are just as open. Only the Admin role can assign the Unrestricted policy. |
Many customers also have custom policies for specific vendor hosts or ports, payment and POS workflows, unique local equipment, or formally approved site exceptions. A globe icon next to a policy marks the company-wide (corporate) version, and a local icon marks a version for this site only. As a rule, if a policy is marked or described as site specific or company specific, don't replace it with a repository or generic imported version without checking first. Scale Computing creates custom policies for you; to request one, contact Scale Computing Support.
Note: Use a standard policy when it clearly matches the device purpose. Use a custom policy only when there is an approved business need the standard policy does not meet. |
For the full policy reference, see the Policies section of the Devices tab documentation.
Before you register a device: key checks
Use these checks before you register a device to avoid issues later.
Authorization. Make sure you have permission to register devices, and that whoever asked for the registration is authorized to request it. These roles can register devices: Admin, Installer, Support Manager, Customer Help Desk, Staff, and Vendor CSR. The Viewer Support Associate role can register devices only by using templates. For details, see Managing user permissions.
Company approval (if required). If your company requires approval from a company administrator before a device is registered, get that approval first.
Device information. Identify what type of device you're registering (for example, a computer, sensor, or printer) and what it needs to communicate with on the network.
Consistency. Review the configuration of other devices at the same site to keep naming conventions, network settings, and policies consistent. Where possible, compare against similar sites in your organization.
Note: Check for any organization-specific guidance first, such as your own documentation, standards, or naming conventions, before relying on the defaults. |
To register a new device
-
Sign in to the SC//AcuVigil dashboard. In the company menu, select Locations, then select the site you want to work with.
-
In the site menu, select Status to open the Site Status page, and check that the site isn't DOWN. For what each status color means, see Site status colors.
-
Select the Devices tab to view and manage the devices for this site.
Sites with managed switches show the SmartSwitch application on this tab. Other sites show Device Manager. The registration steps are the same in both.
-
In the View dropdown menu, select Unregistered.
If there are devices that haven't been registered yet, this view is usually shown by default.
-
Review the list of devices that need registration.
-
Identify devices with fixed IP addresses. Devices that have a static (unchanging) IP address might be highlighted as critical in the list.
-
Select Register Devices.
The Register Devices form lists each unregistered device, with its MAC address and current IP address in the heading.
-
For each device you want to register now, select Add.
-
For any device you don't want to register right now, leave Ignore selected.
Note: If the device replaces one that's already registered, for example a replacement printer, select Swap with registered device instead and choose the old device from the list. Its name, segment, policy, and IP address are copied to the new device, so you don't need to fill in steps 10 through 14.
-
In the Name field, type a descriptive name for the device.
Note: For consistency, use the standard naming convention for your network or follow the naming style of other devices at this site. Naming may be case sensitive and application dependent, so verify the exact name.
-
From the Segment dropdown, choose the network segment (LAN or VLAN) that the device will be connected to.
-
From the IP Address dropdown, choose the correct network address for the device.
Important: Make sure the IP address you select belongs to the same network you chose in step 11. Use the correct assigned IP address from the network design, not just whatever address the device currently has.
-
If a Device Type field is shown, select the correct category (for example, ATG, Card Reader, or DVR). Some solutions and policy suggestions depend on the right device type being set.
-
From the Policy dropdown, select the firewall policy that matches the device's purpose. Avoid permissive policies such as Unrestricted and InternetAccess unless explicitly approved. To register a device without giving it network access, choose Monitor. Only users with the Admin role can assign the Unrestricted policy.
-
From the Error Status dropdown, select the severity used to represent the device's status and to drive alerting: Info, Warning, or Critical. Setting this correctly makes sure the device is monitored and alerts at the right level.
The level you choose is the status the device raises for the site when it stops responding. For example, a non-responding device set to Warning turns the site's status to at least WARNING. If you choose None, a non-responding device doesn't change the site's status and doesn't appear in the Non-Responding Devices Report. Use None only for devices that are expected to be offline sometimes.
-
Select Register Devices to save the settings and complete the registration. To leave without saving, select Cancel.
Important: Don't guess. If a request conflicts with your organization's standards, or if you're unsure about the naming, VLAN, IP plan, or policy choice, stop and verify before saving the registration. |
Registration checklist
- Confirm the requester is authorized.
- Review your organization's documentation or standards.
- Verify the exact device name.
- Verify the VLAN or segment.
- Verify the intended (designed) IP address.
- Verify the device type, if required.
- Apply the correct standard or approved custom policy.
- Set the correct error level.
- Avoid Unrestricted or similar broad policies unless explicitly approved.
Common mistakes to avoid
- Registering the device with the wrong name format
- Using the currently observed IP address instead of the designed IP address
- Putting the device on the wrong VLAN or segment
- Choosing a permissive policy just to make the issue go away
- Ignoring your organization's registration standards
- Forgetting to set the error level
- Overwriting a site-specific or company-specific policy with a generic import
Common issues
Devices not showing up: Make sure the device is powered on and connected to the network, and verify its network connectivity. If it has a static IP address, make sure the address is within the correct subnet and doesn't conflict with another device. You might need to consult your network documentation or a network administrator.