Known Issues

This document lists and describes the known issues and possible workarounds in the NGINX Management Suite Security Monitoring module. Fixed issues are removed after 45 days.

Tip:
We recommend you upgrade to the latest version of the Security Monitoring module to take advantage of new features, improvements, and bug fixes.

1.0.0

The API Connectivity Manager module won’t load if the Security Monitoring module is enabled

Description

If you have Instance Manager 2.7 or earlier installed and attempt to enable both the API Connectivity Manager (ACM) and Security Monitoring (SM) modules on the same NGINX Management Suite management plane, the ACM module will not load because of incompatibility issues with the SM module.

Workaround

Before enabling the ACM and SM modules, ensure that your Instance Manager is upgraded to version 2.8 or later. Be sure to read the release notes for each module carefully, as they may contain important information about version dependencies.

To see which version of Instance Manager you have installed, run the following command:

• CentOS, RHEL, RPM-based:

  yum info nms-instance-manager
  

• Debian, Ubuntu, Deb-based:

  dpkg -s nms-instance-manager
  

The field retrieving URIs is incorrectly listed as URL.

Description

The field with URI data is mapped to the heading URL.

Filtering data by Instance Group in the Security Monitoring module does not show any results.

Description

The Security Monitoring plugin for the NGINX Agent doesn’t automatically pick up changes made to agent-dynamic.conf, causing associated Instance Groups to be missing in security violations.

Workaround

Restart the NGINX Agent, and the subsequent violations should be associated with the Instance Group:

systemctl restart nginx-agent