CNL_CH_13
問題一覧
1
Lessons learned
2
It examines and documents how well the team responded discovers what caused the incident, and determines how the incident can be avoided in the future
3
Train the team to identify the difference between events and incidents
4
The forensic investigator forgot to run a checksum on the disk image after creation
5
User Behavior Analysis
6
Take a memory snapshot of the running system.
7
Command and control
8
Implement a vulnerability scan to assess dependencies earlier on SDLC.
9
Scan the NAS for residual or dormant malware and take new daily backups that are tested on a frequent basis.
10
The provenance of the artifacts, The date time
11
Containment
12
A log analysis
13
Implement a heuristic behavior-detection solution.
14
Geographic dispersal ***
15
dd
16
MITREATT&CK
17
The DNS logs
18
DNS query logs
19
The Diamond Model of intrusion Analysis
20
Bug bounty
21
A tabletop exercise
22
Conducting a tabletop exercise
23
Identification
24
Identification
25
Non-repudiation
26
Lessons learned
27
Pivoting
28
Anonymize any PII that is observed within the IoC data.
29
Screen filters
30
The examiner does not have administrative privileges to the system
31
A communications plan
32
A right-to-audit clause allowing for annual security audits
33
SOAR
34
Cache, memory, temporary filesystems, disk, archival media
35
dd (disk duplication)
36
Data accessibility, Value and volatility of data
37
Chain of custody
38
Updating the playbooks with better decision points
39
Pagefile
40
Isolating the compromised accounts and computers, cutting off all network and internet access.
41
Document the collection and require a sign-off when possession changes.
42
Containment
43
RAM, Cache
44
Creating a playbook within the SOAR
45
Dump
46
Hashing
47
A SOC 2 Type 2 report
48
Legal hold
49
SOAR
50
Lessons learned
51
Put the machine in containment
52
Check the metadata in the email header of the received path in reverse order to follow the email's path.
53
Identification
54
Publish the document in a central repository that is easily accessible to the organization.
55
Communication plan
56
Communication plan
57
Bandwidth monitors
58
CPU cache, memory, temporary filesystems, disk
59
Containment
60
Initiate the organization's incident response plan
61
A supply-chain attack
62
Legal hold
63
Firmware
64
Add SSL/TLS encryption and use a TCP 6514 port to send logs.
65
Place all known-infected hosts on an isolated network
66
Utilize a SOAR playbook to remove the phishing message.
67
Manually uninstall the update that contains the backdoor.
68
Classify all data on the file servers.
69
Containment
70
Data collector
71
Use the latest version of software., Implement a screened subnet for the web server., Install an endpoint security solution.
72
Lessons learned
73
Isolate the device
74
Memory contents including fileless malware are lost when the power is turned off
75
Chain of custody
76
MITREATT&CK
77
Attempt to quarantine all infected hosts to limit further spread.
78
The MITRE ATT&CK framework
79
MITRE ATT&CK
80
Isolate the infected attachment
81
SOAR playbook
82
Write down the phone number of the caller, if possible, the name of the person requesting the information, hang up and notify the organization's cybersecurity officer.
83
Preparation
84
Inspect the file metadata
85
Image volatile memory
86
.Quarantine the host from other parts of the network
87
Chain of custody
88
Lessons learned
89
Set up hashing on the source log file servers that complies with local regulatory requirements.
90
Drop
91
Connect a write blocker to the hard drive Then leveraging a forensic workstation, utilize the dd command on a live Linux environment to create a duplicate copy
92
Attempt to quarantine all infected hosts to limit further spread
93
Tune monitoring in order to reduce false positive rates.
94
Monitoring outbound traffic
95
Order of volatility
CNL_CH_1
CNL_CH_1
Son Cagrı · 3回閲覧 · 185問 · 2年前CNL_CH_1
CNL_CH_1
3回閲覧 • 185問 • 2年前CNL_CH_2
CNL_CH_2
Son Cagrı · 109問 · 2年前CNL_CH_2
CNL_CH_2
109問 • 2年前CNL_CH_3
CNL_CH_3
Son Cagrı · 90問 · 2年前CNL_CH_3
CNL_CH_3
90問 • 2年前CNL_CH_4
CNL_CH_4
Son Cagrı · 48問 · 2年前CNL_CH_4
CNL_CH_4
48問 • 2年前CNL_CH_5
CNL_CH_5
Son Cagrı · 83問 · 2年前CNL_CH_5
CNL_CH_5
83問 • 2年前CNL_CH_6
CNL_CH_6
Son Cagrı · 100問 · 2年前CNL_CH_6
CNL_CH_6
100問 • 2年前CNL_CH_7
CNL_CH_7
Son Cagrı · 43問 · 2年前CNL_CH_7
CNL_CH_7
43問 • 2年前CNL_CH_8
CNL_CH_8
Son Cagrı · 66問 · 2年前CNL_CH_8
CNL_CH_8
66問 • 2年前CNL_CH_9
CNL_CH_9
Son Cagrı · 49問 · 2年前CNL_CH_9
CNL_CH_9
49問 • 2年前CNL_CH_10
CNL_CH_10
Son Cagrı · 75問 · 2年前CNL_CH_10
CNL_CH_10
75問 • 2年前CNL_CH_11
CNL_CH_11
Son Cagrı · 118問 · 2年前CNL_CH_11
CNL_CH_11
118問 • 2年前CNL_CH_12
CNL_CH_12
Son Cagrı · 124問 · 2年前CNL_CH_12
CNL_CH_12
124問 • 2年前21 Mayis
21 Mayis
Son Cagrı · 69問 · 1年前21 Mayis
21 Mayis
69問 • 1年前20 Mayis -175-
20 Mayis -175-
Son Cagrı · 174問 · 1年前20 Mayis -175-
20 Mayis -175-
174問 • 1年前30 Mayis
30 Mayis
Son Cagrı · 209問 · 1年前30 Mayis
30 Mayis
209問 • 1年前A-1
A-1
Son Cagrı · 216問 · 1年前A-1
A-1
216問 • 1年前A-2
A-2
Son Cagrı · 184問 · 1年前A-2
A-2
184問 • 1年前A-3
A-3
Son Cagrı · 68問 · 1年前A-3
A-3
68問 • 1年前exam topics
exam topics
Son Cagrı · 306問 · 1年前exam topics
exam topics
306問 • 1年前pass4future
pass4future
Son Cagrı · 330問 · 1年前pass4future
pass4future
330問 • 1年前son 1
son 1
Son Cagrı · 349問 · 1年前son 1
son 1
349問 • 1年前son 2
son 2
Son Cagrı · 113問 · 1年前son 2
son 2
113問 • 1年前son 3
son 3
Son Cagrı · 63問 · 1年前son 3
son 3
63問 • 1年前問題一覧
1
Lessons learned
2
It examines and documents how well the team responded discovers what caused the incident, and determines how the incident can be avoided in the future
3
Train the team to identify the difference between events and incidents
4
The forensic investigator forgot to run a checksum on the disk image after creation
5
User Behavior Analysis
6
Take a memory snapshot of the running system.
7
Command and control
8
Implement a vulnerability scan to assess dependencies earlier on SDLC.
9
Scan the NAS for residual or dormant malware and take new daily backups that are tested on a frequent basis.
10
The provenance of the artifacts, The date time
11
Containment
12
A log analysis
13
Implement a heuristic behavior-detection solution.
14
Geographic dispersal ***
15
dd
16
MITREATT&CK
17
The DNS logs
18
DNS query logs
19
The Diamond Model of intrusion Analysis
20
Bug bounty
21
A tabletop exercise
22
Conducting a tabletop exercise
23
Identification
24
Identification
25
Non-repudiation
26
Lessons learned
27
Pivoting
28
Anonymize any PII that is observed within the IoC data.
29
Screen filters
30
The examiner does not have administrative privileges to the system
31
A communications plan
32
A right-to-audit clause allowing for annual security audits
33
SOAR
34
Cache, memory, temporary filesystems, disk, archival media
35
dd (disk duplication)
36
Data accessibility, Value and volatility of data
37
Chain of custody
38
Updating the playbooks with better decision points
39
Pagefile
40
Isolating the compromised accounts and computers, cutting off all network and internet access.
41
Document the collection and require a sign-off when possession changes.
42
Containment
43
RAM, Cache
44
Creating a playbook within the SOAR
45
Dump
46
Hashing
47
A SOC 2 Type 2 report
48
Legal hold
49
SOAR
50
Lessons learned
51
Put the machine in containment
52
Check the metadata in the email header of the received path in reverse order to follow the email's path.
53
Identification
54
Publish the document in a central repository that is easily accessible to the organization.
55
Communication plan
56
Communication plan
57
Bandwidth monitors
58
CPU cache, memory, temporary filesystems, disk
59
Containment
60
Initiate the organization's incident response plan
61
A supply-chain attack
62
Legal hold
63
Firmware
64
Add SSL/TLS encryption and use a TCP 6514 port to send logs.
65
Place all known-infected hosts on an isolated network
66
Utilize a SOAR playbook to remove the phishing message.
67
Manually uninstall the update that contains the backdoor.
68
Classify all data on the file servers.
69
Containment
70
Data collector
71
Use the latest version of software., Implement a screened subnet for the web server., Install an endpoint security solution.
72
Lessons learned
73
Isolate the device
74
Memory contents including fileless malware are lost when the power is turned off
75
Chain of custody
76
MITREATT&CK
77
Attempt to quarantine all infected hosts to limit further spread.
78
The MITRE ATT&CK framework
79
MITRE ATT&CK
80
Isolate the infected attachment
81
SOAR playbook
82
Write down the phone number of the caller, if possible, the name of the person requesting the information, hang up and notify the organization's cybersecurity officer.
83
Preparation
84
Inspect the file metadata
85
Image volatile memory
86
.Quarantine the host from other parts of the network
87
Chain of custody
88
Lessons learned
89
Set up hashing on the source log file servers that complies with local regulatory requirements.
90
Drop
91
Connect a write blocker to the hard drive Then leveraging a forensic workstation, utilize the dd command on a live Linux environment to create a duplicate copy
92
Attempt to quarantine all infected hosts to limit further spread
93
Tune monitoring in order to reduce false positive rates.
94
Monitoring outbound traffic
95
Order of volatility