--- title: "Restricted SNMP write access for third-party NMS users" slug: "restricted-snmp-write-access-for-third-party-nms-users-2" tags: ["Product Usage", "IPS 11.1.x"] updated: 2026-11-19T12:30:36Z published: 2026-11-19T12:30:36Z canonical: "docs.trellix.com/restricted-snmp-write-access-for-third-party-nms-users-2" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # Restricted SNMP write access for third-party NMS users Sensors provide read-write access to a Host Quarantine Group portion of the MIB tree. To have read-write access to these MIBs, the following configurations are needed: - Configure third-party NMS users. - Configure a set of IPv4/IPv6 addresses from where third-party SNMP access would be allowed. For managing the restricted read-write access, you need to enable/disable it from the Sensor CLI. For more information, see the CLI commands section. After enabling/disabling the access, the Sensor is to be rebooted only if the SNMP users are already configured. If no SNMP user is configured on the Sensor, then the configuration is done without rebooting the Sensor. The following write operations are permitted: - Add an IPv4/IPv6 entry to quarantine the host. - Extend the quarantine duration of an existing quarantined IPv4/IPv6 host entry. - Delete the IPv4/IPv6 filter entries one by one. - Delete all the IPv4/IPv6 filter entries at once. - Remediation for IPv4. If the Sensor is in the failover mode, make sure that the entries are created on both the primary and secondary Sensors. Restricted read-write access is permitted for the section of the MIB tree depicted in the following image. ![GUID-C967D209-43FE-4B47-9EA7-8EF384453623-low.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-f51f3ae3-7785-d86a-6833-0806ad129f06(7).png?sv=2026-02-06&spr=https&st=2026-11-20T12%3A14%3A41Z&se=2026-11-20T13%3A14%3A41Z&sr=c&sp=r&sig=k1NdRQWtjar%2Bl7D5mH64%2BPvqJTTbk3bmDqHnXjMBRis%3D) ### User scenarios **Scenario 1** To isolate a host in the Sensor from the third-party SNMP application: Set the **hostQUserDefFilterAction** object of the **hostIsolUserDefFilterTable** to a value 1. For setting this object, the following indices are needed: - IP Address (To be provided in a dot separated format) - VidsId (should always be set to 0) - AttackId (should always be set to 0) The above action is applicable to both IPv4 as well as IPv6 entries. Consider the following example: For isolating a host with IPv4 address of **10.12.12.15**, the following OID is to be set with a value 1. OID - 1.3.6.1.4.1.8962.2.1.2.1.22.6.1.5.**10.12.12.15**.0.0 **Scenario 2** To extend the isolation end time of an already isolated host in the Sensor from the third-party SNMP application: Set the **hostQUserDefFilterDuration** object of the **hostIsolUserDefFilterTable** to a value