To reduce the risk of unauthorized BYOD (Bring Your Own Device) usage, the organization should implement Conditional Access and Network Access Control (NAC).
Why Conditional Access and NAC?
Conditional Access:
User-to-Device Binding: Conditional access policies can enforce that only registered and compliant devices are allowed to access corporate resources.
Context-Aware Security: Enforces access controls based on the context of the access attempt, such as user identity, device compliance, location, and more.
Network Access Control (NAC):
DeviceConfiguration Requirements: NAC ensures that only devices meeting specific security configurations are allowed to connect to the network.
Access Control: Provides granular control over network access, ensuring that BYOD devices comply with security policies before gaining access.
Other options, while useful, do not address the specific need to control and secure BYOD devices effectively:
A. Cloud IAM to enforce token-based MFA: Enhances authentication security but does not control device compliance.
D. PAM to enforce local password policies: Focuses on privileged account management, not BYOD control.
E. SD-WAN to enforce web content filtering: Enhances network performance and security but does not enforce BYOD device compliance.
F. DLP to enforce data protection capabilities: Protects data but does not control BYOD device access and compliance.
[References:, CompTIA SecurityX Study Guide, "Conditional Access Policies," Microsoft Documentation, "Network Access Control (NAC)," Cisco Documentation, , , , , , ]
Submit