Skip to content

Cyber ark#751

Closed
JimmyJamTQBD wants to merge 3 commits into
Azure:masterfrom
JimmyJamTQBD:CyberArk
Closed

Cyber ark#751
JimmyJamTQBD wants to merge 3 commits into
Azure:masterfrom
JimmyJamTQBD:CyberArk

Conversation

@JimmyJamTQBD
Copy link
Copy Markdown
Contributor

Fixes #

Proposed Changes

Copy link
Copy Markdown
Contributor

@preetikr preetikr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I also see a commit from someone else which is Playbooks/Get-MDATPVulnerabilities/report_template.docx included in this PR.
Please drop this file else it'll overwrite what we already have in the repo. It'll be great to clean up the branch or do this PR / changes from a new branch to avoid picking up random changes.

@@ -54,7 +54,7 @@
},
{
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please move the CyberArk workbook to https://github.com/Azure/Azure-Sentinel/tree/master/Workbooks folder and follow guidance @ https://github.com/Azure/Azure-Sentinel/tree/master/Workbooks#how-to-contribute-new-workbook to submit the workbook.
The Dashboards folder is going to be deleted soon.

@@ -0,0 +1,46 @@
# Connect CyberArk to Azure Sentinel
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please email us the md file and remove this file from this PR - the documentation for data connector goes to a different repository and should not be in this repo. Thanks.

@@ -0,0 +1,104 @@
{
"id": "CyberArk",
"title": "CyberArk Enterprise Password Vault (EPV) Syslog",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You might want to remove Syslog from the title as it's basically a CEF connector

"id": "CyberArk",
"title": "CyberArk Enterprise Password Vault (EPV) Syslog",
"publisher": "Cyber-Ark",
"descriptionMarkdown": "CyberArk Enterprise Password Vault generates an xml Syslog messages for every action taken against the Vault. The EPV will send the xml messages through the Sentinel.xsl translator to be converted into CEF standard format and sent to a syslog staging server of your choice (syslog-ng, rsyslog). The Log Analytics agent installed on your syslog staging server will import the messages into Azure Log Analytics",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. Syslog message is right grammatically since it's 'generates an xml Syslog messages' which seems incorrect. Please fix.
  2. It'd be great to also add a link to CyberArk product documentation.

"sampleQueries": [
{
"description" : "CyberArk Alerts",
"query": "\nCommonSecurityLog\n| where LogSeverity == \"7\" or LogSeverity == \"10\"\n| sort by TimeGenerated desc"
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This will get all results from not only CyberArk but also any other products that have LogSeverity.
Add a where clause as follows before the LogSeverity clause.
| where DeviceVendor == "Cyber-Ark"

],
"dataTypes": [
{
"name": "CommonSecurityLog",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The data type name should be "CommonSecurityLog (CyberArk)" with values in the parenthesis same as the value in the legend name.

"graphQueries": [
{
"metricName": "Total data received",
"legend": "CyberArkSyslog",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You can have the legend as just CyberArk - the syslog term is confusing.

},
{
"title": "1.2 Install the CEF collector on the Linux machine",
"description": "Install the Microsoft Monitoring Agent on your Linux machine and configure the machine to listen on the necessary port and forward messages to your Azure Sentinel workspace. The CEF collector colects CEF messages on port 514 TCP.\n\n> 1. Make sure that you have Python on your machine using the following command: python –version.\n\n> 2. You must have elevated permissions (sudo) on your machine.",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In step #1 there are ASCII / weird chars trailing python - 'following command: python �version.'
Please delete chars after python and delete parts of version and retype to remove this.

},
{
"title": "2. Forward Common Event Format (CEF) logs to Syslog agent",
"description": "On the EPV configure the dbparm.ini to send Syslog messages in CEF format to the proxy machine. Make sure you to send the logs to port 514 TCP on the machine’s IP address."
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In step #2 as well there are ASCII / weird chars trailing machine - 'TCP on the machine�s IP address.'
Please delete chars after machine and delete parts of IP and retype to remove this.

},
{
"title": "3. Validate connection",
"description": "Follow the instructions to validate your connectivity:\n\nOpen Log Analytics to check if the logs are received using the CommonSecurityLog schema.\n\n>It may take about 20 minutes until the connection streams data to your workspace.\n\nIf the logs are not received, run the following connectivity validation script:\n\n> 1. Make sure that you have Python on your machine using the following command: python –version\n\n>2. You must have elevated permissions (sudo) on your machine",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In step 3 (point 1) as well there are ASCII / weird chars trailing python - 'following command: python �version'
Please delete chars after python and delete parts of version and retype to remove this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants