問題一覧
1
TA-
2
Workstations, notebooks, and point-of-sale systems.
3
$fieldname$
4
Threat Download Manager
5
Authentication
6
Run the correct search.
7
ess_analyst
8
Priority
9
An aggregation.
10
All indexes
11
tstatsHomePath
12
Run a | datamodel search, compare results to the CIM documentation for the datamodel.
13
summariesonly=t
14
Click the "Add IOC" button.
15
Configure -> Content Management -> Select Type "Correlation" and Status "Enabled"
16
Indexes have different settings.
17
Web, Authentication, Network Traffic
18
Splunk_TA_ForIndexers.spl is installed first.
19
Window duration.
20
Recommended Actions show a list of Adaptive Responses to an analyst, Adaptive Response Actions run them automatically.
21
A high-level overview of notable events.
22
A device.
23
Upload the lookup file using Configure -> Content Management -> Create New Content -> Managed Lookup
24
Security metrics.
25
Customization.
26
Configure -> Content Management -> Type: Correlation Search -> Notable -> Recommended Actions -> Nslookup
27
Configure -> Incident Management -> Incident Review Settings -> Table Attributes
28
Protocol Analysis
29
cim_modactions
30
Reducing the severity.
31
SplunkBase
32
A prefix of Splunk_TA_
33
$SPLUNK_HOME/etc/shcluster/apps
34
Severity set by the correlation search and priority assigned to the associated asset or identity.
35
A risk score.
36
Configure -> Content Management
37
STIX/TAXII
38
Add a new search head and install ES on it.
39
Data models
40
The search head.
41
Email.
42
Normalize data.
43
100 GB
44
No other apps.
45
Scheduled
46
KV Store
47
Risk
48
Configure -> General -> Navigation
49
OS: 64 bit, RAM: 12 MB, CPU: 16 cores
50
A display of the highest risk assets and identities.
51
Either use new app names or always include both existing and new content.
52
ess_admin users only.
53
Splunk_TA_ForIndexers.spl
54
Edit the search, look for where or xswhere statements, and after the threshold value being compared to make it less common match.
55
Reduce the frequency (schedule) of lower-priority correlation searches.
56
Protocol intelligence dashboard.
57
SA-CIM.
58
Data integrity control.
59
Determine the size and scope of installation.
60
5 minutes
61
3.4
62
Configure the add-ons according to their README or documentation.
63
Any content type listed in the Content Management page.
64
On a server with a new install of Splunk.
65
From the Status Configuration window select the Resolved status. Remove ess_user from the status transitions for the Closed status.
66
Add additional forwarders.
67
Increase memory and CPUs on the search head(s) and add additional indexers.
68
Field alias.
69
Threat intel.
70
Modify the correlation schedule and sensitivity for your site.
71
From the Edit Navigation page, drag and drop the Threat Activity View to the top of the page.
72
indexes.conf, props.conf, transforms.conf
73
Correlation Searches
74
The Identity Lookup CSV file.
75
The Event Details.
76
Set the dashboard permissions to allow access by es_analysts and use the navigation editor to add it to the menu.
77
The Investigation Bar.
78
Priority and Severity.
79
Events in the threat activity index.
80
Configuring correlation adaptive responses.
81
ip, mac, dns, nt_host
82
Searches only accelerated data.
83
SplunkWeb (8000), splunk Management (8089), KV Store (8191)
84
Identifies on which data model(s) each dashboard depends.
85
Configure search head forwarding.
86
By custom tech add-ons and users on the risk analysis dashboard.
87
Create notable event
88
$fieldname$
89
Identities
90
indexes.conf
91
Use the tStatsHomePath setting in indexes.conf
92
Map to data models.
93
The Corporate Web and Email Domain Lookups are edited during initial configuration.
94
Searches can be built no matter the specific source technology for a normalized data type.
95
Configuring user and website watchlists so the User Activity dashboard Will highlight unwanted user actions.
96
HTTP Category Analysis
97
Normalization to the Splunk Common Information Model.
98
Server
99
Protocol Intelligence dashboards.
問題一覧
1
TA-
2
Workstations, notebooks, and point-of-sale systems.
3
$fieldname$
4
Threat Download Manager
5
Authentication
6
Run the correct search.
7
ess_analyst
8
Priority
9
An aggregation.
10
All indexes
11
tstatsHomePath
12
Run a | datamodel search, compare results to the CIM documentation for the datamodel.
13
summariesonly=t
14
Click the "Add IOC" button.
15
Configure -> Content Management -> Select Type "Correlation" and Status "Enabled"
16
Indexes have different settings.
17
Web, Authentication, Network Traffic
18
Splunk_TA_ForIndexers.spl is installed first.
19
Window duration.
20
Recommended Actions show a list of Adaptive Responses to an analyst, Adaptive Response Actions run them automatically.
21
A high-level overview of notable events.
22
A device.
23
Upload the lookup file using Configure -> Content Management -> Create New Content -> Managed Lookup
24
Security metrics.
25
Customization.
26
Configure -> Content Management -> Type: Correlation Search -> Notable -> Recommended Actions -> Nslookup
27
Configure -> Incident Management -> Incident Review Settings -> Table Attributes
28
Protocol Analysis
29
cim_modactions
30
Reducing the severity.
31
SplunkBase
32
A prefix of Splunk_TA_
33
$SPLUNK_HOME/etc/shcluster/apps
34
Severity set by the correlation search and priority assigned to the associated asset or identity.
35
A risk score.
36
Configure -> Content Management
37
STIX/TAXII
38
Add a new search head and install ES on it.
39
Data models
40
The search head.
41
Email.
42
Normalize data.
43
100 GB
44
No other apps.
45
Scheduled
46
KV Store
47
Risk
48
Configure -> General -> Navigation
49
OS: 64 bit, RAM: 12 MB, CPU: 16 cores
50
A display of the highest risk assets and identities.
51
Either use new app names or always include both existing and new content.
52
ess_admin users only.
53
Splunk_TA_ForIndexers.spl
54
Edit the search, look for where or xswhere statements, and after the threshold value being compared to make it less common match.
55
Reduce the frequency (schedule) of lower-priority correlation searches.
56
Protocol intelligence dashboard.
57
SA-CIM.
58
Data integrity control.
59
Determine the size and scope of installation.
60
5 minutes
61
3.4
62
Configure the add-ons according to their README or documentation.
63
Any content type listed in the Content Management page.
64
On a server with a new install of Splunk.
65
From the Status Configuration window select the Resolved status. Remove ess_user from the status transitions for the Closed status.
66
Add additional forwarders.
67
Increase memory and CPUs on the search head(s) and add additional indexers.
68
Field alias.
69
Threat intel.
70
Modify the correlation schedule and sensitivity for your site.
71
From the Edit Navigation page, drag and drop the Threat Activity View to the top of the page.
72
indexes.conf, props.conf, transforms.conf
73
Correlation Searches
74
The Identity Lookup CSV file.
75
The Event Details.
76
Set the dashboard permissions to allow access by es_analysts and use the navigation editor to add it to the menu.
77
The Investigation Bar.
78
Priority and Severity.
79
Events in the threat activity index.
80
Configuring correlation adaptive responses.
81
ip, mac, dns, nt_host
82
Searches only accelerated data.
83
SplunkWeb (8000), splunk Management (8089), KV Store (8191)
84
Identifies on which data model(s) each dashboard depends.
85
Configure search head forwarding.
86
By custom tech add-ons and users on the risk analysis dashboard.
87
Create notable event
88
$fieldname$
89
Identities
90
indexes.conf
91
Use the tStatsHomePath setting in indexes.conf
92
Map to data models.
93
The Corporate Web and Email Domain Lookups are edited during initial configuration.
94
Searches can be built no matter the specific source technology for a normalized data type.
95
Configuring user and website watchlists so the User Activity dashboard Will highlight unwanted user actions.
96
HTTP Category Analysis
97
Normalization to the Splunk Common Information Model.
98
Server
99
Protocol Intelligence dashboards.