Idea ID: 2705148

ArcMC to manage all ArcSight products and components

Status: Accepted

Add process automation orchestration supporting ArcSight component and product infrastructure management through ArcSight-provided workflows.

Minimally will manage and/or monitor: Connectors, Thub and Kafka, Logger, ESM, Investigate, Certificates, Licensing, ...

OpenText Community Manager
If you found this post useful, give it a “Like” or click on "Verify Answer" under the "More" button

Parents
  • I agree with multiple replies here.
    Struggles with our current deployment include:

    • Managing ESM separately
    • Managing load balancers separately
    • Having to manually created users via ArcMC and then sink them down to our many Loggers.
      • Using AD security groups would be wonderful. 
      • Not exposed via API either.
    • Having to manage users with ESM separately.
      • Again, AD security groups. 
      • Not exposed via API.
    • Manually pulling down Logger, ESM, ArcMC updates from the entitlement portal and deploy them. 
      • Once pushed to ArcMC, Logger, Connector, and ArcMC updates are relatively easy (though they sometime require manual steps).
      • ESM is a whole different beast. Lots of manual steps, some of which, in theory, can be automated, but not the whole process. 
    • Exposure of more functionality through the REST API. Mainly for automation purposes.
      • Consistency of API is also key here, so that developed code can be partially reused. 
Comment
  • I agree with multiple replies here.
    Struggles with our current deployment include:

    • Managing ESM separately
    • Managing load balancers separately
    • Having to manually created users via ArcMC and then sink them down to our many Loggers.
      • Using AD security groups would be wonderful. 
      • Not exposed via API either.
    • Having to manage users with ESM separately.
      • Again, AD security groups. 
      • Not exposed via API.
    • Manually pulling down Logger, ESM, ArcMC updates from the entitlement portal and deploy them. 
      • Once pushed to ArcMC, Logger, Connector, and ArcMC updates are relatively easy (though they sometime require manual steps).
      • ESM is a whole different beast. Lots of manual steps, some of which, in theory, can be automated, but not the whole process. 
    • Exposure of more functionality through the REST API. Mainly for automation purposes.
      • Consistency of API is also key here, so that developed code can be partially reused. 
Children
No Data