Wireless network certificate validating identity
These draft guidelines promote resiliency in the platform by describing security mechanisms for protecting the platform against unauthorized changes, detecting unauthorized changes that occur, and secure recovery from attacks.This document is intended to guide implementers, including system manufacturers and and component suppliers, on how to use these mechanisms to build a strong security foundation into platforms.To provide federal agencies with examples of how the Cybersecurity Framework can augment the current versions of NIST security and privacy risk management publications, this guidance uses common federal information security vocabulary and processes.NIST will engage with agencies to add content based on agency implementation, refine current guidance and identify additional guidance to provide the information that is most helpful to agencies.This chapter examines the relationship between authentication and authorization and how to build policies for each, describing a few common Authentication Policies and Authorization Policies to help you see how to work with these policy constructs.
The specific guidance was derived from current Cybersecurity Framework use.
I suspect a firmware upgrade probably fixes that behaviour. If you want to accept both computer credentials and user credentials you'll need to name both "Domain Comptuers" and "Domain Users" in your policy.
By default, XP will re-authenticate with the user credential after the user logs-on (there is no way to do computer-only with XP, I believe).
To understand Authentication Policies even more, let’s examine a few.
From the ISE GUI, navigate to Policy Rules are processed in a top-down, first-match order; just like a firewall policy.
Feedback will also help to determine which Cybersecurity Framework concepts are incorporated into future versions of the suite of NIST security and privacy risk management publications.