VMware AppDefense
The JSA DSM for VMware AppDefense collects events from a VMware AppDefense
To integrate VMware AppDefense with JSA, complete the following steps:
- If automatic updates are not enabled, download and install
the most recent version of the following RPMs on your JSA console:
Protocol Common RPM
VMWare AppDefense API Protocol RPM
DSMCommon RPM
VMWare AppDefense DSM RPM
- Configure your VMware AppDefense to send events to JSA.
- Add a VMware AppDefense log source that uses the VMware AppDefense API on the JSA Console.
VMWare AppDefense DSM Specifications
The following table describes the specifications for the VMWare AppDefense DSM.
Table 1: VMWare AppDefense DSM Specifications
Specification | Value |
---|---|
Manufacturer | VMware |
DSM name | VMWare AppDefense |
RPM file name | DSM-VMWare AppDefenseJSA-version-Build_number.noarch.rpm |
Supported versions | V1.0 |
Protocol | VMWare AppDefense API |
Event format | JSON |
Recorded event types | All |
Automatically discovered? | No |
Includes identity? | No |
Includes custom properties? | No |
More information |
The JSA DSM for VMware AppDefense collects events from a VMware AppDefense system.
Configuring VMware AppDefense to Communicate with JSA
To send events to JSA from your VMware AppDefense system, you must create a new API key on your VMware AppDefense system.
Ensure that you have access to the Integrations settings in the VMware AppDefense user interface so that you can generate the Endpoint URL and API Key that are required to configure a log source in JSA. You must have the correct user permissions for the VMware AppDefense user interface to complete the following procedure:
- Log in to your VMware AppDefense user interface.
- From the navigation menu, click the icon to the right of your user name, and then select Integrations.
- Click PROVISION NEW API KEY.
- In the Integration Name field, type a name for your integration.
- Select an integration from the Integration Type list.
- Click PROVISION, and then record and save the
following information from the message in the window that opens. You
need this information when you configure a log source in JSA:
EndPoint URL
API Key - This is the Authentication Token parameter value when you configure a log source in JSA.
Note If you click OK or close the window, the information in the message can't be recovered.
Configuring a VMware AppDefense Log Source by using the VMWare AppDefense API Protocol
If you want to collect VMware AppDefense logs from VMware AppDefense, add a log source on the JSA Console so that VMware AppDefense can communicate with JSA by using the VMWare AppDefense API protocol.
- Log in to JSA.
- Click the Admin tab.
- Click the Log Sources icon.
- Click Add.
- From the Log Source Type list, select VMWare AppDefense.
Where <Tenant ID> is a UUID.
- From the Protocol Configuration list, select VMWare AppDefense API.
- Configure the parameters.
The following table describes the parameters that require specific values to collect JSON events from VMware AppDefense by using the VMWare AppDefense API protocol:
Table 2: VMWare AppDefense API Protocol Log Source Parameters
Specification
Value
Log Source Type
VMWare AppDefense
Protocol Configuration
VMWare AppDefense API
Endpoint URL
The endpoint URL for accessing VMware AppDefense. Example revision:https://server_name.vmwaredrx.com/partnerapi/v1/ orgs/<organization ID>
Authentication Token
A single authentication token that is generated by the AppDefense console and must be used for all API transactions.
Use Proxy
If JSA accesses the VMWare AppDefense API by using a proxy, enable Use Proxy.
If the proxy requires authentication, configure the Hostname, Proxy Port, Proxy Username, and Proxy fields.
If the proxy does not require authentication, configure the Hostname and Proxy Port fields.
Automatically Acquire Server Certificate(s)
If you choose Yes from the drop down list, JSA automatically downloads the certificate and begins trusting the target server. If No is selected JSA does not attempt to retrieve any server certificates.
Recurrence
Beginning at the Start Time, type the frequency for how often you want the remote directory to be scanned. Type this value in hours(H), minutes(M), or days(D). For example, 2H if you want the directory to be scanned every 2 hours. The default is 5M.
EPS Throttle
The maximum number of events per second.
The default is 5000.
- Click Save.
- On the Admin tab, click Deploy Changes.
VMware AppDefense Sample Event Messages
Table 3: VMware AppDefense Sample Message Supported by VMware AppDefense.
Event name | Low level category | Sample log message |
---|---|---|
Inbound Connection Rule Violation | Firewall Deny | {"id":1111111,"createdAt":1512009263.471000000, "remediation":{"id":1111111},"severity":"CRITICAL",
"lastReceivedAt":1516170726.957000000,"count":2, "status":"UNRESOLVED","violationDetails":{"processHa
shSHA256":"10000000000000000000000000000000000000000 00000000000000000000000","processHash":"100000000000
00000000000000000000","cli":"<cli>”, “localPort":"<24
","processPath":"","alert":"INBOUND_CONNECTION_RULES _VIOLATION","localAddress":"192.0.2.0","ipProtocol":
"tcp","preEstablishedConnection":"FALSE"},"violating VirtualMachine":{"id":1111111,"vmToolsStatus":"TOOLS
_NOT_RUNNING","vcenterUuid":"11111111-1111-1111-1111 -111111111111","vmUuid":"11111111-1111-1111-1111-111
111111111","ipAddress":"192.0.2.0”,"osType":"WINDOWS ","vmManageabilityStatus":"HOST_MODULE_ENABLED_AND_ |
Outbound Connection Rule Violation | Firewall Deny | {"id":10101001,"createdAt":1512009263.495000000, "remediation":{"id":1551519},"severity":"CRITICAL",
"lastReceivedAt":1516224258.818000000,"count":0000 1,"status":"UNRESOLVED","violationDetails":{"proce
ssHashSHA256":"00000000000000000000000000000000000 00000000000000000000000000","processHash":"0000000
000000000000000000000000","cli":"C:\\<path>path>,"alert" :"OUTBOUND_CONNECTION_RULES_VIOLATION","localAddre
ss":"192.0.2.0","remotePort":"24","ipProtocol": "udp","preEstablishedConnection":"FALSE","remote
Address":"0000::0:0"},"violatingVirtualMachine": {"id":101010,"vmToolsStatus":"TOOLS_NOT_RUNNING",
"vcenterUuid":"11111111-1111-1111-1111-1111111111 11","vmUuid":"11111111-1111-1111-1111-11111111111
1","ipAddress":"192.0.2.0","osType":"WINDOWS","vm ManageabilityStatus":"HOST_MODULE_ENABLED_AND_GUE
ST_MODULE_MISSING", |