問題一覧
1
- The presence of this vulnerability indicates that the domain security policy may be lacking appropriate controls.
2
- Exposure to external networks
3
- Port 23
4
- The scans are being blocked by a rule within the web server application.
5
- The shim (application compatibility) cache
6
- Fuzz testing
7
- A printer
8
- Exploit developers
9
- Charles cannot determine if there are hosts on the network segment from this scan.
10
- BIA
11
- SSH
12
- Review the contents of the scalpelout folder.
13
- Web
14
- CVSS
15
- Indicators of compromise
16
- Internal network vulnerability scan
17
- That the username used was gnome
18
- High network bandwidth consumption
19
- Evidence production procedure
20
- Preparation
21
- Gloria should perform both internal and external scans of the server.
22
- Clear it
23
- Set system BIOS/UEFI clocks regularly.
24
- Windows
25
- Phishing
26
- Check the system's MAC address against known assets.
27
- The control must include a clear audit mechanism.
28
- Replace the certificate
29
- Media life span
30
- 1. Availability, 2. Confidentiality, 3. Integrity
31
- Upgrade OpenSSH.
32
- Segmentation
33
- She can use this data to determine a reasonable response time baseline.
34
- File carving
35
- Search for a core dump or hibernation file to analyze.
36
- <SCRIPT>
37
- Using a heuristic detection rule on an IPS
38
- The target system's operating system.
39
- SOAR
40
- A DVD-ROM
41
- A SYN flood
42
- Use the ATA Secure Erase command.
43
- Data classification
44
- The scanning program must include, at a minimum, weekly scans of the internal network.
45
- Patching the server
46
- OS detection
47
- Jose should discuss his opinion with his manager and request that the remediation criteria be changed.
48
- Sandboxing
49
- SLE
50
- Adjust the scanning frequency to avoid scanning during peak times.
51
- Restoring from backup may reintroduce the original vulnerability
52
- The malware removed itself after losing network connectivity.
53
- ISO 27001
54
- /etc/shadow
55
- Implement logging.
56
- Approve an exception for this server.
57
- The map version identification is using the banner to determine the service version.
58
- Initiate the change management process.
59
- Nessus
60
- Containment, eradication, and recovery
61
- The Center for Internet Security
62
- The organization or individual that discovered the vulnerability
63
- Beaconing
64
- Regulatory compliance
65
- AbuselPDB
66
- A SLO
67
- A script kiddie
68
- Mean time to compromise
69
- Data enrichment
70
- Organizational policies
71
- Timeliness, relevance, and accuracy
72
- Segmentation
73
- topdump
74
- A report showing remediation and patching trends
75
- Potential data exfiltration
76
- Mean time to defend
77
- Time synchronization
78
- A compensating control
79
- Irregular peer-to-peer communication
80
- Perform stakeholder identification.
81
- SPF
82
- A lack of update to the original cluster image
83
- The Dark Web
84
- Hardware tokens
85
- API-based integration
THE P.T: 1 CHRONICLE: ( ex.9 )
THE P.T: 1 CHRONICLE: ( ex.9 )
The R.S.S.H Delivery Company · 90問 · 6ヶ月前THE P.T: 1 CHRONICLE: ( ex.9 )
THE P.T: 1 CHRONICLE: ( ex.9 )
90問 • 6ヶ月前THE P.T: 2 CHRONICLE: ( ex.10 )
THE P.T: 2 CHRONICLE: ( ex.10 )
The R.S.S.H Delivery Company · 88問 · 6ヶ月前THE P.T: 2 CHRONICLE: ( ex.10 )
THE P.T: 2 CHRONICLE: ( ex.10 )
88問 • 6ヶ月前THE P.T. 3: CHRONICLE: ( ex.12 )
THE P.T. 3: CHRONICLE: ( ex.12 )
The R.S.S.H Delivery Company · 89問 · 6ヶ月前THE P.T. 3: CHRONICLE: ( ex.12 )
THE P.T. 3: CHRONICLE: ( ex.12 )
89問 • 6ヶ月前THE P.T. 4: CHRONICLE: ( ex.11 )
THE P.T. 4: CHRONICLE: ( ex.11 )
The R.S.S.H Delivery Company · 52問 · 6ヶ月前THE P.T. 4: CHRONICLE: ( ex.11 )
THE P.T. 4: CHRONICLE: ( ex.11 )
52問 • 6ヶ月前THE P.T. 5: CHRONICLE: ( ex.13 )
THE P.T. 5: CHRONICLE: ( ex.13 )
The R.S.S.H Delivery Company · 92問 · 6ヶ月前THE P.T. 5: CHRONICLE: ( ex.13 )
THE P.T. 5: CHRONICLE: ( ex.13 )
92問 • 6ヶ月前THE P.T. 6: CHRONICLE: ( ex.14 )
THE P.T. 6: CHRONICLE: ( ex.14 )
The R.S.S.H Delivery Company · 90問 · 6ヶ月前THE P.T. 6: CHRONICLE: ( ex.14 )
THE P.T. 6: CHRONICLE: ( ex.14 )
90問 • 6ヶ月前THE P.T. 7: ( ex.15 )
THE P.T. 7: ( ex.15 )
The R.S.S.H Delivery Company · 48問 · 6ヶ月前THE P.T. 7: ( ex.15 )
THE P.T. 7: ( ex.15 )
48問 • 6ヶ月前EXAM #1 |
EXAM #1 |
The R.S.S.H Delivery Company · 90問 · 7ヶ月前EXAM #1 |
EXAM #1 |
90問 • 7ヶ月前1 ) Identify Security Control Types
1 ) Identify Security Control Types
The R.S.S.H Delivery Company · 5問 · 9ヶ月前1 ) Identify Security Control Types
1 ) Identify Security Control Types
5問 • 9ヶ月前2 ) Threat Intelligence
2 ) Threat Intelligence
The R.S.S.H Delivery Company · 8問 · 9ヶ月前2 ) Threat Intelligence
2 ) Threat Intelligence
8問 • 9ヶ月前EXAM #2 |
EXAM #2 |
The R.S.S.H Delivery Company · 90問 · 7ヶ月前EXAM #2 |
EXAM #2 |
90問 • 7ヶ月前3 ) Classifying Threats
3 ) Classifying Threats
The R.S.S.H Delivery Company · 17問 · 9ヶ月前3 ) Classifying Threats
3 ) Classifying Threats
17問 • 9ヶ月前EXAM # 3 |
EXAM # 3 |
The R.S.S.H Delivery Company · 90問 · 7ヶ月前EXAM # 3 |
EXAM # 3 |
90問 • 7ヶ月前4 ) Threat Hunting
4 ) Threat Hunting
The R.S.S.H Delivery Company · 16問 · 9ヶ月前4 ) Threat Hunting
4 ) Threat Hunting
16問 • 9ヶ月前EXAM # 4 |
EXAM # 4 |
The R.S.S.H Delivery Company · 90問 · 7ヶ月前EXAM # 4 |
EXAM # 4 |
90問 • 7ヶ月前5 ) Network Forensics
5 ) Network Forensics
The R.S.S.H Delivery Company · 9問 · 9ヶ月前5 ) Network Forensics
5 ) Network Forensics
9問 • 9ヶ月前EXAM # 5 |
EXAM # 5 |
The R.S.S.H Delivery Company · 90問 · 7ヶ月前EXAM # 5 |
EXAM # 5 |
90問 • 7ヶ月前問題一覧
1
- The presence of this vulnerability indicates that the domain security policy may be lacking appropriate controls.
2
- Exposure to external networks
3
- Port 23
4
- The scans are being blocked by a rule within the web server application.
5
- The shim (application compatibility) cache
6
- Fuzz testing
7
- A printer
8
- Exploit developers
9
- Charles cannot determine if there are hosts on the network segment from this scan.
10
- BIA
11
- SSH
12
- Review the contents of the scalpelout folder.
13
- Web
14
- CVSS
15
- Indicators of compromise
16
- Internal network vulnerability scan
17
- That the username used was gnome
18
- High network bandwidth consumption
19
- Evidence production procedure
20
- Preparation
21
- Gloria should perform both internal and external scans of the server.
22
- Clear it
23
- Set system BIOS/UEFI clocks regularly.
24
- Windows
25
- Phishing
26
- Check the system's MAC address against known assets.
27
- The control must include a clear audit mechanism.
28
- Replace the certificate
29
- Media life span
30
- 1. Availability, 2. Confidentiality, 3. Integrity
31
- Upgrade OpenSSH.
32
- Segmentation
33
- She can use this data to determine a reasonable response time baseline.
34
- File carving
35
- Search for a core dump or hibernation file to analyze.
36
- <SCRIPT>
37
- Using a heuristic detection rule on an IPS
38
- The target system's operating system.
39
- SOAR
40
- A DVD-ROM
41
- A SYN flood
42
- Use the ATA Secure Erase command.
43
- Data classification
44
- The scanning program must include, at a minimum, weekly scans of the internal network.
45
- Patching the server
46
- OS detection
47
- Jose should discuss his opinion with his manager and request that the remediation criteria be changed.
48
- Sandboxing
49
- SLE
50
- Adjust the scanning frequency to avoid scanning during peak times.
51
- Restoring from backup may reintroduce the original vulnerability
52
- The malware removed itself after losing network connectivity.
53
- ISO 27001
54
- /etc/shadow
55
- Implement logging.
56
- Approve an exception for this server.
57
- The map version identification is using the banner to determine the service version.
58
- Initiate the change management process.
59
- Nessus
60
- Containment, eradication, and recovery
61
- The Center for Internet Security
62
- The organization or individual that discovered the vulnerability
63
- Beaconing
64
- Regulatory compliance
65
- AbuselPDB
66
- A SLO
67
- A script kiddie
68
- Mean time to compromise
69
- Data enrichment
70
- Organizational policies
71
- Timeliness, relevance, and accuracy
72
- Segmentation
73
- topdump
74
- A report showing remediation and patching trends
75
- Potential data exfiltration
76
- Mean time to defend
77
- Time synchronization
78
- A compensating control
79
- Irregular peer-to-peer communication
80
- Perform stakeholder identification.
81
- SPF
82
- A lack of update to the original cluster image
83
- The Dark Web
84
- Hardware tokens
85
- API-based integration