Re: Activate Development

Hey everyone, if you're currently working on a project, please add your contact information. It can be your e-mail address, or your P724 account info for private messages. For contacting HPE folks, that shouldn't be too difficult, since our usernames are our real names (not sure that was such a great idea...). If you are a customer and have a handle, rather than your real name, please make sure someone can contact you.

Re: Activate Development

Hi Aizuevo,

Yes, We are working in L1 & L2 Malware Monitoring package, as well as some Anti-Malware ( virus ) product packages. Once they are available in the marketplace We would like to have your feedback on them!

Re: Activate Development

Hey

is still testing this, and he has not yet submitted it to the ArcSight Marketplace. I'm sure that once he's gotten significant testing completed, he will publish the package and its documentation on the Activate Wiki.

Re: Activate Development

Hello, all.

This question is probably for Prentice, but defintely for anyone developing Activate packages.Two things:

Firstly, at the moment, there are two product packages that I require for a current client that do not have installer .BAT files: Cisco ASA and Palo Alto. The Palo Alto wiki documentation is incomplete/template, so I assume that I import the .ARB via the console per usual. Will that accomplish all that is required? I assume so, but wanted to ask.

The Cisco ASA wiki docs describe the .BAT file process for package v1.2.0.0, but package v 1.1.0.1, with no .BAT, is available on Marketplace. Should Cisco ASA v1.2.0.0 be out there, or so I just go ahead and import v1.1.0.1 .ARB via console, as per the PAN package, or shoudl I wait for the v1.2.0.0 package to catch up with the wiki documentation?

Secondly, what is the preferred method for reporting issues in the packages? The L2 Perimeter v0.1.0.0 package has a couple of broken references in Rules to an Active List that it expects in the old Perimeter and Network Monitoring legacy folder (pre-split) which is in fact in the Core/Common (??) folder now. The L2 Network v0.1.0.0 package has a Rule referencing an Active List which does not exist anywhere that I can find, so I will have to create it. Not sure of all the parameters for that AL, but I can create based on what I glean from the .XML file, key fields being the possible outliers.

Re: Activate Development

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.