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 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.

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 Horizon Energy Services: Network devices have inconsistent local clock settings and VPN troubleshooting logs do not align. The relevant corrective control for this case is: Configure reliable authenticated NTP sources and verify synchronization status.

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 Horizon Energy Services: Network devices have inconsistent local clock settings and VPN troubleshooting logs do not align. The relevant corrective control for this case is: Configure reliable authenticated NTP sources and verify synchronization status.

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 Horizon Energy Services: Network devices have inconsistent local clock settings and VPN troubleshooting logs do not align. The relevant corrective control for this case is: Configure reliable authenticated NTP sources and verify synchronization status.

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 Horizon Energy Services was resolved. The specific required evidence is: Tunnel events from both peers share an interpretable timestamp sequence.

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 Horizon Energy Services was resolved. The specific required evidence is: Tunnel events from both peers share an interpretable timestamp sequence.

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 Horizon Energy Services was resolved. The specific required evidence is: Tunnel events from both peers share an interpretable timestamp sequence.

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 Newbridge Charity: Network devices have inconsistent local clock settings and VPN troubleshooting logs do not align. The relevant corrective control for this case is: Configure reliable authenticated NTP sources and verify synchronization status.

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 Newbridge Charity: Network devices have inconsistent local clock settings and VPN troubleshooting logs do not align. The relevant corrective control for this case is: Configure reliable authenticated NTP sources and verify synchronization status.

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 Newbridge Charity: Network devices have inconsistent local clock settings and VPN troubleshooting logs do not align. The relevant corrective control for this case is: Configure reliable authenticated NTP sources and verify synchronization status.

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 Newbridge Charity was resolved. The specific required evidence is: Tunnel events from both peers share an interpretable timestamp sequence.

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 Newbridge Charity was resolved. The specific required evidence is: Tunnel events from both peers share an interpretable timestamp sequence.

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 Newbridge Charity was resolved. The specific required evidence is: Tunnel events from both peers share an interpretable timestamp sequence.

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 Harbor Point Medical: An automation client uses a certificate with the wrong server name yet ignores TLS errors. The relevant corrective control for this case is: Validate peer certificate chains and hostnames for API and RESTCONF management calls.

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 Harbor Point Medical: An automation client uses a certificate with the wrong server name yet ignores TLS errors. The relevant corrective control for this case is: Validate peer certificate chains and hostnames for API and RESTCONF management calls.

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 Harbor Point Medical: An automation client uses a certificate with the wrong server name yet ignores TLS errors. The relevant corrective control for this case is: Validate peer certificate chains and hostnames for API and RESTCONF management calls.

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 Harbor Point Medical was resolved. The specific required evidence is: An impostor certificate fails the test and a valid management endpoint succeeds.

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 Harbor Point Medical was resolved. The specific required evidence is: An impostor certificate fails the test and a valid management endpoint succeeds.

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 Harbor Point Medical was resolved. The specific required evidence is: An impostor certificate fails the test and a valid management endpoint succeeds.

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 Clearbrook University: An automation client uses a certificate with the wrong server name yet ignores TLS errors. The relevant corrective control for this case is: Validate peer certificate chains and hostnames for API and RESTCONF management calls.

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 Clearbrook University: An automation client uses a certificate with the wrong server name yet ignores TLS errors. The relevant corrective control for this case is: Validate peer certificate chains and hostnames for API and RESTCONF management calls.

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 Clearbrook University: An automation client uses a certificate with the wrong server name yet ignores TLS errors. The relevant corrective control for this case is: Validate peer certificate chains and hostnames for API and RESTCONF management calls.

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 Clearbrook University was resolved. The specific required evidence is: An impostor certificate fails the test and a valid management endpoint succeeds.

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 Clearbrook University was resolved. The specific required evidence is: An impostor certificate fails the test and a valid management endpoint succeeds.

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 Clearbrook University was resolved. The specific required evidence is: An impostor certificate fails the test and a valid management endpoint succeeds.

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 Oceanview Payments: Administrators transfer backups over unencrypted FTP to a shared server. The relevant corrective control for this case is: Use SCP or SFTP to protected storage with least-privilege service credentials.

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 Oceanview Payments: Administrators transfer backups over unencrypted FTP to a shared server. The relevant corrective control for this case is: Use SCP or SFTP to protected storage with least-privilege service credentials.

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 Oceanview Payments: Administrators transfer backups over unencrypted FTP to a shared server. The relevant corrective control for this case is: Use SCP or SFTP to protected storage with least-privilege service credentials.

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 Oceanview Payments was resolved. The specific required evidence is: A backup transfer is encrypted and stored with access and integrity controls.

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 Oceanview Payments was resolved. The specific required evidence is: A backup transfer is encrypted and stored with access and integrity controls.

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 Oceanview Payments was resolved. The specific required evidence is: A backup transfer is encrypted and stored with access and integrity controls.