Exam Bundle

A backup transfer is encrypted and stored with access and integrity controls. This would be relevant evidence for a different failure: Administrators transfer backups over unencrypted FTP to a shared server, usually addressed by Use SCP or SFTP to protected storage with least-privilege service credentials. It does not demonstrate that the current problem at Briarwood Property Group was resolved. The specific required evidence is: An authorized test changes only an approved configuration subtree and an untrusted client is denied.

A packet inspection shows protected monitoring traffic and a v2c attempt is rejected. This would be relevant evidence for a different failure: Monitoring credentials are sent in plaintext SNMPv2c strings across untrusted paths, usually addressed by Use SNMPv3 authPriv where supported and restrict manager addresses. It does not demonstrate that the current problem at Briarwood Property Group was resolved. The specific required evidence is: An authorized test changes only an approved configuration subtree and an untrusted client is denied.

The collector receives trustworthy events while a forged or unprotected feed is rejected. This would be relevant evidence for a different failure: A security appliance's syslog packets cross an untrusted segment without integrity or confidentiality controls, usually addressed by Use protected syslog transport and authenticated collectors according to supported capabilities. It does not demonstrate that the current problem at Briarwood Property Group was resolved. The specific required evidence is: An authorized test changes only an approved configuration subtree and an untrusted client is denied.

Configure reliable authenticated NTP sources and verify synchronization status. That action fits another problem: Network devices have inconsistent local clock settings and VPN troubleshooting logs do not align. It does not directly remediate the current finding at Arborstone Tech: A network automation service modifies device configuration over an unauthenticated legacy protocol. The relevant corrective control for this case is: Adopt authenticated, encrypted NETCONF or RESTCONF transport with role-specific permissions.

Limit management HTTPS to an approved admin network with strong authentication. That action fits another problem: A router permits HTTPS management from Internet addresses without IP-based or identity restrictions. It does not directly remediate the current finding at Arborstone Tech: A network automation service modifies device configuration over an unauthenticated legacy protocol. The relevant corrective control for this case is: Adopt authenticated, encrypted NETCONF or RESTCONF transport with role-specific permissions.

Use protected syslog transport and authenticated collectors according to supported capabilities. That action fits another problem: A security appliance's syslog packets cross an untrusted segment without integrity or confidentiality controls. It does not directly remediate the current finding at Arborstone Tech: A network automation service modifies device configuration over an unauthenticated legacy protocol. The relevant corrective control for this case is: Adopt authenticated, encrypted NETCONF or RESTCONF transport with role-specific permissions.

Untrusted clients cannot reach the interface and approved administrators can connect. This would be relevant evidence for a different failure: A router permits HTTPS management from Internet addresses without IP-based or identity restrictions, usually addressed by Limit management HTTPS to an approved admin network with strong authentication. It does not demonstrate that the current problem at Arborstone Tech was resolved. The specific required evidence is: An authorized test changes only an approved configuration subtree and an untrusted client is denied.

Tunnel events from both peers share an interpretable timestamp sequence. This would be relevant evidence for a different failure: Network devices have inconsistent local clock settings and VPN troubleshooting logs do not align, usually addressed by Configure reliable authenticated NTP sources and verify synchronization status. It does not demonstrate that the current problem at Arborstone Tech was resolved. The specific required evidence is: An authorized test changes only an approved configuration subtree and an untrusted client is denied.

The collector receives trustworthy events while a forged or unprotected feed is rejected. This would be relevant evidence for a different failure: A security appliance's syslog packets cross an untrusted segment without integrity or confidentiality controls, usually addressed by Use protected syslog transport and authenticated collectors according to supported capabilities. It does not demonstrate that the current problem at Arborstone Tech was resolved. The specific required evidence is: An authorized test changes only an approved configuration subtree and an untrusted client is denied.

Adopt authenticated, encrypted NETCONF or RESTCONF transport with role-specific permissions. That action fits another problem: A network automation service modifies device configuration over an unauthenticated legacy protocol. It does not directly remediate the current finding at Sapphire Data Systems: A security appliance's syslog packets cross an untrusted segment without integrity or confidentiality controls. The relevant corrective control for this case is: Use protected syslog transport and authenticated collectors according to supported capabilities.

Use SNMPv3 authPriv where supported and restrict manager addresses. That action fits another problem: Monitoring credentials are sent in plaintext SNMPv2c strings across untrusted paths. It does not directly remediate the current finding at Sapphire Data Systems: A security appliance's syslog packets cross an untrusted segment without integrity or confidentiality controls. The relevant corrective control for this case is: Use protected syslog transport and authenticated collectors according to supported capabilities.

Limit management HTTPS to an approved admin network with strong authentication. That action fits another problem: A router permits HTTPS management from Internet addresses without IP-based or identity restrictions. It does not directly remediate the current finding at Sapphire Data Systems: A security appliance's syslog packets cross an untrusted segment without integrity or confidentiality controls. The relevant corrective control for this case is: Use protected syslog transport and authenticated collectors according to supported capabilities.

A packet inspection shows protected monitoring traffic and a v2c attempt is rejected. This would be relevant evidence for a different failure: Monitoring credentials are sent in plaintext SNMPv2c strings across untrusted paths, usually addressed by Use SNMPv3 authPriv where supported and restrict manager addresses. It does not demonstrate that the current problem at Sapphire Data Systems was resolved. The specific required evidence is: The collector receives trustworthy events while a forged or unprotected feed is rejected.

An authorized test changes only an approved configuration subtree and an untrusted client is denied. This would be relevant evidence for a different failure: A network automation service modifies device configuration over an unauthenticated legacy protocol, usually addressed by Adopt authenticated, encrypted NETCONF or RESTCONF transport with role-specific permissions. It does not demonstrate that the current problem at Sapphire Data Systems was resolved. The specific required evidence is: The collector receives trustworthy events while a forged or unprotected feed is rejected.

Untrusted clients cannot reach the interface and approved administrators can connect. This would be relevant evidence for a different failure: A router permits HTTPS management from Internet addresses without IP-based or identity restrictions, usually addressed by Limit management HTTPS to an approved admin network with strong authentication. It does not demonstrate that the current problem at Sapphire Data Systems was resolved. The specific required evidence is: The collector receives trustworthy events while a forged or unprotected feed is rejected.

Validate peer certificate chains and hostnames for API and RESTCONF management calls. That action fits another problem: An automation client uses a certificate with the wrong server name yet ignores TLS errors. It does not directly remediate the current finding at Eastport Research Hospital: A security appliance's syslog packets cross an untrusted segment without integrity or confidentiality controls. The relevant corrective control for this case is: Use protected syslog transport and authenticated collectors according to supported capabilities.

Limit management HTTPS to an approved admin network with strong authentication. That action fits another problem: A router permits HTTPS management from Internet addresses without IP-based or identity restrictions. It does not directly remediate the current finding at Eastport Research Hospital: A security appliance's syslog packets cross an untrusted segment without integrity or confidentiality controls. The relevant corrective control for this case is: Use protected syslog transport and authenticated collectors according to supported capabilities.

Configure reliable authenticated NTP sources and verify synchronization status. That action fits another problem: Network devices have inconsistent local clock settings and VPN troubleshooting logs do not align. It does not directly remediate the current finding at Eastport Research Hospital: A security appliance's syslog packets cross an untrusted segment without integrity or confidentiality controls. The relevant corrective control for this case is: Use protected syslog transport and authenticated collectors according to supported capabilities.

Tunnel events from both peers share an interpretable timestamp sequence. This would be relevant evidence for a different failure: Network devices have inconsistent local clock settings and VPN troubleshooting logs do not align, usually addressed by Configure reliable authenticated NTP sources and verify synchronization status. It does not demonstrate that the current problem at Eastport Research Hospital was resolved. The specific required evidence is: The collector receives trustworthy events while a forged or unprotected feed is rejected.

An impostor certificate fails the test and a valid management endpoint succeeds. This would be relevant evidence for a different failure: An automation client uses a certificate with the wrong server name yet ignores TLS errors, usually addressed by Validate peer certificate chains and hostnames for API and RESTCONF management calls. It does not demonstrate that the current problem at Eastport Research Hospital was resolved. The specific required evidence is: The collector receives trustworthy events while a forged or unprotected feed is rejected.

Untrusted clients cannot reach the interface and approved administrators can connect. This would be relevant evidence for a different failure: A router permits HTTPS management from Internet addresses without IP-based or identity restrictions, usually addressed by Limit management HTTPS to an approved admin network with strong authentication. It does not demonstrate that the current problem at Eastport Research Hospital was resolved. The specific required evidence is: The collector receives trustworthy events while a forged or unprotected feed is rejected.

Adopt authenticated, encrypted NETCONF or RESTCONF transport with role-specific permissions. That action fits another problem: A network automation service modifies device configuration over an unauthenticated legacy protocol. It does not directly remediate the current finding at Frostline Distribution: A router permits HTTPS management from Internet addresses without IP-based or identity restrictions. The relevant corrective control for this case is: Limit management HTTPS to an approved admin network with strong authentication.

Use protected syslog transport and authenticated collectors according to supported capabilities. That action fits another problem: A security appliance's syslog packets cross an untrusted segment without integrity or confidentiality controls. It does not directly remediate the current finding at Frostline Distribution: A router permits HTTPS management from Internet addresses without IP-based or identity restrictions. The relevant corrective control for this case is: Limit management HTTPS to an approved admin network with strong authentication.

Configure reliable authenticated NTP sources and verify synchronization status. That action fits another problem: Network devices have inconsistent local clock settings and VPN troubleshooting logs do not align. It does not directly remediate the current finding at Frostline Distribution: A router permits HTTPS management from Internet addresses without IP-based or identity restrictions. The relevant corrective control for this case is: Limit management HTTPS to an approved admin network with strong authentication.

An authorized test changes only an approved configuration subtree and an untrusted client is denied. This would be relevant evidence for a different failure: A network automation service modifies device configuration over an unauthenticated legacy protocol, usually addressed by Adopt authenticated, encrypted NETCONF or RESTCONF transport with role-specific permissions. It does not demonstrate that the current problem at Frostline Distribution was resolved. The specific required evidence is: Untrusted clients cannot reach the interface and approved administrators can connect.

Tunnel events from both peers share an interpretable timestamp sequence. This would be relevant evidence for a different failure: Network devices have inconsistent local clock settings and VPN troubleshooting logs do not align, usually addressed by Configure reliable authenticated NTP sources and verify synchronization status. It does not demonstrate that the current problem at Frostline Distribution was resolved. The specific required evidence is: Untrusted clients cannot reach the interface and approved administrators can connect.

The collector receives trustworthy events while a forged or unprotected feed is rejected. This would be relevant evidence for a different failure: A security appliance's syslog packets cross an untrusted segment without integrity or confidentiality controls, usually addressed by Use protected syslog transport and authenticated collectors according to supported capabilities. It does not demonstrate that the current problem at Frostline Distribution was resolved. The specific required evidence is: Untrusted clients cannot reach the interface and approved administrators can connect.

Configure reliable authenticated NTP sources and verify synchronization status. That action fits another problem: Network devices have inconsistent local clock settings and VPN troubleshooting logs do not align. It does not directly remediate the current finding at Aster Mutual: A router permits HTTPS management from Internet addresses without IP-based or identity restrictions. The relevant corrective control for this case is: Limit management HTTPS to an approved admin network with strong authentication.

Validate peer certificate chains and hostnames for API and RESTCONF management calls. That action fits another problem: An automation client uses a certificate with the wrong server name yet ignores TLS errors. It does not directly remediate the current finding at Aster Mutual: A router permits HTTPS management from Internet addresses without IP-based or identity restrictions. The relevant corrective control for this case is: Limit management HTTPS to an approved admin network with strong authentication.

Use SCP or SFTP to protected storage with least-privilege service credentials. That action fits another problem: Administrators transfer backups over unencrypted FTP to a shared server. It does not directly remediate the current finding at Aster Mutual: A router permits HTTPS management from Internet addresses without IP-based or identity restrictions. The relevant corrective control for this case is: Limit management HTTPS to an approved admin network with strong authentication.

A backup transfer is encrypted and stored with access and integrity controls. This would be relevant evidence for a different failure: Administrators transfer backups over unencrypted FTP to a shared server, usually addressed by Use SCP or SFTP to protected storage with least-privilege service credentials. It does not demonstrate that the current problem at Aster Mutual was resolved. The specific required evidence is: Untrusted clients cannot reach the interface and approved administrators can connect.

An impostor certificate fails the test and a valid management endpoint succeeds. This would be relevant evidence for a different failure: An automation client uses a certificate with the wrong server name yet ignores TLS errors, usually addressed by Validate peer certificate chains and hostnames for API and RESTCONF management calls. It does not demonstrate that the current problem at Aster Mutual was resolved. The specific required evidence is: Untrusted clients cannot reach the interface and approved administrators can connect.

Tunnel events from both peers share an interpretable timestamp sequence. This would be relevant evidence for a different failure: Network devices have inconsistent local clock settings and VPN troubleshooting logs do not align, usually addressed by Configure reliable authenticated NTP sources and verify synchronization status. It does not demonstrate that the current problem at Aster Mutual was resolved. The specific required evidence is: Untrusted clients cannot reach the interface and approved administrators can connect.