A software company requires devices used by staff to be recognized by the identity platform before sign-in. After deploying new laptops, staff members are unable to sign in, even though the credentials are correct. The logs contain a warning that the device is not recognized, and there is no sign of malicious activity. Which action would likely resolve these sign-in denials?
Add the new laptops to the trust settings so they pass device verification
Extend the rotation schedule for keys to match laptop provisioning
Turn off device verification and rely on username plus passcodes
Allow local administrator privileges on new laptops for staff
Acknowledging the new devices in the identity platform’s trust settings aligns them with existing rules. Staff can then sign in without unauthorized access concerns. Granting local administrator privileges or disabling device-based checks bypasses the original security controls, increasing risk. Adjusting key rotation schedules does not address recognition issues for new hardware.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
Why is device verification important in identity platforms?
Open an interactive chat with Bash
How does an identity platform recognize trusted devices?
Open an interactive chat with Bash
What are the risks of bypassing device verification with username and passcode only?