Network access or admission control is a form of client/endpoint security that uses a locally installed software agent to pre-authorize connections to a protected network. NAC
screens client devices for contamination by known malware and adherence to security policies such as running an approved OS with the most recent patches. Clients that fail NAC screens are rerouted to an isolated quarantine network until any detected problems are corrected. In the Common Information Model, NAC data is typically mapped to the Network Sessions data model.
NAC data provide security teams with a detailed profile of a client’s state and activity. They can provide details into unauthorized device connections and be used to correlate users/IP to a physical network location.
When your Splunk deployment is ingesting NAC data, you can use it to accomplish security and compliance use cases.
Guidance for onboarding data can be found in the Spunk Documentation, Getting Data In (Splunk Enterprise) or Getting Data In (Splunk Cloud). In addition, these Splunk Add-Ons and Apps are helpful for working with NAC data.
Looking for more information on data types? Download the Splunk Essential Guide to Machine Data.