Edit

MarkLogic Audit connector for Microsoft Sentinel

  • Article

MarkLogic data connector provides the capability to ingest MarkLogicAudit logs into Microsoft Sentinel. Refer to MarkLogic documentation for more information.

Connector attributes

Connector attribute Description
Log Analytics table(s) MarkLogicAudit_CL
Data collection rules support Not currently supported
Supported by Microsoft Corporation

Query samples

MarkLogicAudit - All Activities.

MarkLogicAudit_CL

| sort by TimeGenerated desc

Vendor installation instructions

NOTE: This data connector depends on a parser based on a Kusto Function to work as expected which is deployed as part of the solution. To view the function code in Log Analytics, open Log Analytics/Microsoft Sentinel Logs blade, click Functions and search for the alias MarkLogicAudit and load the function code or click here on the second line of the query, enter the hostname(s) of your MarkLogicAudit device(s) and any other unique identifiers for the logstream. The function usually takes 10-15 minutes to activate after solution installation/update.

  1. Install and onboard the agent for Linux or Windows

Install the agent on the Tomcat Server where the logs are generated.

Logs from MarkLogic Server deployed on Linux or Windows servers are collected by Linux or Windows agents.

  1. Configure MarkLogicAudit to enable auditing

Perform the following steps to enable auditing for a group:

Access the Admin Interface with a browser;

Open the Audit Configuration screen (Groups > group_name > Auditing);

Select True for the Audit Enabled radio button;

Configure any audit events and/or audit restrictions you want;

Click OK.

Refer to the MarkLogic documentation for more details

  1. Configure the logs to be collected

Configure the custom log directory to be collected

  1. Select the link above to open your workspace advanced settings
  2. From the left pane, select Settings, select Custom Logs and click +Add custom log
  3. Click Browse to upload a sample of a MarkLogicAudit log file. Then, click Next >
  4. Select Timestamp as the record delimiter and click Next >
  5. Select Windows or Linux and enter the path to MarkLogicAudit logs based on your configuration
  6. After entering the path, click the '+' symbol to apply, then click Next >
  7. Add MarkLogicAudit as the custom log Name (the '_CL' suffix will be added automatically) and click Done.

Validate connectivity

It may take upwards of 20 minutes until your logs start to appear in Microsoft Sentinel.

Next steps

For more information, go to the related solution in the Azure Marketplace.