This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

L2-Perimeter Monitoring - Situational Awareness

This is the official forum for the discussion of the L2-Perimeter Monitoring - Situational Awareness package.

 

This content is coming soon!

 

The installation/update package will be available from the ArcSight Marketplace. All new and updated Activate Framework packages will be made available on the ArcSight Marketplace (https://marketplace.microfocus.com/arcsight).

 

The documentation is available at https://hpe-sec.com/foswiki/bin/view/ArcSightActivate/L2PerimeterMonitoring .

--
Prentice S. Hayes
Principal Product Manager | Cybersecurity Enterprise, Security Analytics
OpenText Cybersecurity

LinkedIn: https://www.linkedin.com/in/prenticeshayes/ 

Website: https://www.opentext.com/

Parents
  • 0

    ​

    Also wondering if Perimeter & Network Monitoring package is split into following 4 different packages then why I still see a folder\group "Perimeter and Network Monitoring" (See the selected group in the screenshot)

    L1-Perimeter Monitoring - Indicators and Warnings

    L2-Perimeter Monitoring - Situational Awareness

    L1-Network Monitoring - Indicators and Warnings

    L2-Network Monitoring - Situational Awareness

  • 0   in reply to 

    If you upgraded from the L<1|2>-Perimeter and Network Monitoring packages, then it is possible that some of the groups didn't get cleaned up when you (or the update scripts) uninstalled them. If you had them installed and uninstalled them, then installed the new versions, they probably weren't cleaned up.

    There are several reasons why they might not have been cleaned up with their parent package uninstallation. The most common being that some of the resources in the group were modified or were somehow linked to resources outside of the package. Worst-case, there was something not quite properly cleaned up in the DB. You should be able to delete the offending groups. They're not in the new packages.

    --
    Prentice S. Hayes
    Principal Product Manager | Cybersecurity Enterprise, Security Analytics
    OpenText Cybersecurity

    LinkedIn: https://www.linkedin.com/in/prenticeshayes/ 

    Website: https://www.opentext.com/

Reply
  • 0   in reply to 

    If you upgraded from the L<1|2>-Perimeter and Network Monitoring packages, then it is possible that some of the groups didn't get cleaned up when you (or the update scripts) uninstalled them. If you had them installed and uninstalled them, then installed the new versions, they probably weren't cleaned up.

    There are several reasons why they might not have been cleaned up with their parent package uninstallation. The most common being that some of the resources in the group were modified or were somehow linked to resources outside of the package. Worst-case, there was something not quite properly cleaned up in the DB. You should be able to delete the offending groups. They're not in the new packages.

    --
    Prentice S. Hayes
    Principal Product Manager | Cybersecurity Enterprise, Security Analytics
    OpenText Cybersecurity

    LinkedIn: https://www.linkedin.com/in/prenticeshayes/ 

    Website: https://www.opentext.com/

Children
No Data