Environment
NetIQ Access Manager 3.2
NetIQ Access Manager 3.2 Support Pack 1 applied
Peneration tests performed against all NAM components
Access Gateway Appliance failing penetration test
NetIQ Access Manager 3.2 Support Pack 1 applied
Peneration tests performed against all NAM components
Access Gateway Appliance failing penetration test
Situation
Access Manager 3.2 setup and working fine. Prior to rolling out in production, a penetration test for PCI compliance was performed against all components. A number of components tested came back reporting support for weak ciphers. By following the best practice guidelines in the documentation, the Identity Server, Embedded Service provider support cipher list under server.xml were changed to only include strong ciphers; the Apache proxy configuration was also modified to include striong cipher support using the SSProxyCipherSuite Advanced Option.
One test continued to fail against TCP port 61617 - the SSL port used by ActiveMQ. there appeared to be no configuration files where the ciphers could be manually changed.
One test continued to fail against TCP port 61617 - the SSL port used by ActiveMQ. there appeared to be no configuration files where the ciphers could be manually changed.
Resolution
Modify the /etc/opt/novell/activemq/activemq.xml file and change the localhost entry to specifically state 61617 as shown below:
<transportConnector name="ssl" uri="ssl://127.0.0.1:61617"/>
This will block any access to the ActiveMQ SSL service from deices other than localhost.
Another option would be to use iptables to block access to this TCP port from any host other than localhost.
<transportConnector name="ssl" uri="ssl://127.0.0.1:61617"/>
This will block any access to the ActiveMQ SSL service from deices other than localhost.
Another option would be to use iptables to block access to this TCP port from any host other than localhost.