You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This unpublished material is proprietary to Phantom Cyber.
7
-
All rights reserved. The methods and
8
-
techniques described herein are considered trade secrets
9
-
and/or confidential. Reproduction or distribution, in whole
10
-
or in part, is forbidden except by express written permission
11
-
of Phantom Cyber.
4
+
SPLUNK CONFIDENTIAL - Use or disclosure of this material in whole or in part
5
+
without a valid written license from Splunk Inc. is PROHIBITED.
12
6
-->
13
-
14
-
<p>
7
+
<h2>On Poll</h2>
15
8
<h3>Ingestion</h3>
16
-
During the first scheduled poll, all incidents that fall in the <b>first_scheduled_ingestion_span</b> will be ingested.
17
-
<br><br>
18
-
During a <b>POLL NOW</b>, incidents will be ingested starting with the most recent. The number of incidents ingested will depend on the specified <b>max_containers</b> and <b>poll_now_ingestion_span</b>, whichever limit is hit first.
19
-
</p>
9
+
10
+
<h4> Schedule | Interval Polling </h4>
11
+
<ul>
12
+
<li>During scheduled | interval polling, the app will start from the number of days specified in <b>first_scheduled_ingestion_span</b> and will ingest up to the number of incidents specified in the <b>max_containers</b> (Default value 10) in configuration parameter per cycle. Then it remembers the last ingested 'incident_id' and stores it in the state file against the key 'last_incident_ingested'. For the next scheduled | interval cycles, ingestion will start from the last_incident_ingested in the state file and will ingest up to the number of incidents specified in the <b>max_containers</b>.</li>
13
+
<li>The number of incidents ingested will depend on the specified <b>max_containers</b> and <b>poll_now_ingestion_span</b>, whichever limit is hit first.</li>
14
+
</ul>
15
+
<h4> Manual Polling </h4>
16
+
<ul>
17
+
<li>
18
+
During a <b>POLL NOW</b>, incidents will be ingested starting with the oldest first. The number of incidents ingested will depend on the specified <b>max_containers</b> and <b>poll_now_ingestion_span</b>, whichever limit is hit first.
19
+
</li>
20
+
</ul>
21
+
<b>Custom Severity Config Parameter</b>
22
+
<ul>
23
+
<li>
24
+
It is an optional parameter. Here the user needs to provide a JSON string in the following format
This parameter can be used to map the Symantec DLP incident severity to any of the custom phantom severity.
27
+
</li>
28
+
<li>
29
+
To configure a custom severity in the Phantom, go to Administrator → Event Settings → Severity. Click on 'add item' and give an appropriate name for the severity and click on 'Done' button.
30
+
</li>
31
+
<li>
32
+
By default, the severity is mapped in the following way:
33
+
<ul>
34
+
<li>
35
+
For the incident having 'high' severity, the container's severity will be 'high'.
36
+
</li>
37
+
<li>
38
+
For the incident having 'medium' severity, the container's severity will be 'medium'.
39
+
</li>
40
+
<li>
41
+
For the incident having 'low' severity, the container's severity will be 'low'.
42
+
</li>
43
+
<li>
44
+
For the incident having severity other than 'high', 'low' or 'medium' the container's severity will be 'medium'.
0 commit comments