- Basics
- About Knox
- Knox licenses
- Knox white paper
- Sign up for Samsung Knox
- Latest release notes
- General Knox FAQ
- General Knox KBAs
- Submit a support ticket
- User Acceptance Testing
- For IT admins
- Knox Admin Portal
- Knox Suite
- Knox Platform for Enterprise
- Introduction
- How-to videos
- Before you begin
- Get started with UEMs
- Introduction
- Blackberry UEM
- Citrix Endpoint Management
- FAMOC
- IBM MaaS360
- Microsoft Intune
- MobileIron Cloud
- MobileIron Core
- Samsung Knox Manage
- SOTI MobiControl
- VMware Workspace ONE UEM
- Knox Service Plugin
- Release notes
- Migrate to Android 11
- FAQs
- Troubleshoot
- KBAs
- Knox Mobile Enrollment
- Knox Configure
- Mobile
- Wearables
- Shared Device
- FAQ
- KBAs
- Knox Capture
- Introduction
- How it works
- How-to videos
- IT admins: Get started
- Getting started with Knox Capture
- Step 1: Launch Knox Capture
- Step 2: Create a scanning profile
- Step 3: Select apps and activities
- Step 4: Configure the scanner
- Step 5: Set keystroke output rules
- Step 6: Test apps in your configuration
- Step 7: Share your configuration
- Step 8: Deploy Knox Capture in Managed mode
- End users: Get started
- Features
- Release notes
- FAQ
- KBAs
- Troubleshoot
- Knox Asset Intelligence
- Knox Manage
- Introduction
- How-to videos
- Get started
- Video: Getting started with Knox Manage
- Integration with Managed Service Provider
- Access Knox Manage
- Configure basic environments
- Create user accounts
- Create groups
- Create organization
- Set up devices and profiles
- Create a new profile
- Assign profiles to groups and organizations
- Enroll devices
- Shared Android device quickstart
- Non-shared Android device enrollment quickstart
- Android Management API device enrollment quickstart
- Apple User Enrollment quickstart
- View device information
- Apply profiles to organizations
- Set up Knox Manage deployment with a Knox Suite license
- Manage Chromebooks
- Manage Android devices with the Android Management API
- Manage Shared iPads
- Configure
- Licenses
- Organization
- Users
- Sync user information
- Groups
- Devices
- Content
- Applications
- Profile
- Knox E-FOTA
- Certificates
- Advanced settings
- Monitor
- Kiosk devices
- Knox Remote Support
- Active Directory
- Microsoft Exchange
- Mobile Admin
- Appendix
- Release notes
- Features
- FAQ
- KBAs
- Knox E-FOTA
- Introduction
- How-to videos
- Get started
- Features
- EMM integration
- Appendix
- Release notes
- FAQ
- KBAs
- Troubleshoot
- Knox E-FOTA On-Premises
- Legacy Knox E-FOTA products
- Knox Guard
- Introduction
- How-to video
- Get started
- Using Knox Guard
- Dashboard
- Manage devices
- Device management
- Accept or reject devices
- Upload devices
- Delete devices
- Complete device management
- Send notifications
- Enable or disable SIM control
- Download devices as CSV
- View device log
- View device deletion log
- Start and stop blinking reminder
- Lock and unlock devices
- Update lock message
- Send relock timestamp
- Turn on/off relock reminder
- Manage policies
- Manage licenses
- Manage resellers
- Manage admins and roles
- Activity log
- Knox Deployment App
- Release notes
- FAQ
- KBAs
- Support
- Open API reference
- Samsung Care+ for Business
- For Knox Partners
- Knox Deployment Program
- Knox MSP Program
Network
Platform Analytics
Network Platform Analytics (NPA) clients are the IT admin's primary method of monitoring and sorting through the traffic on the devices in their network. NPA clients can monitor and collect a wide variety of details about network traffic, including—but not limited to—the following information:
- Application from where the request originated
- Origin and target IP address information
- Encryption level and protocol details
- Amount of data packets sent and received
The process to enable and configure the NPA client to collect information is in two stages:
Create an NPA Data Points profile
KSP uses an NPA Data Points profile to configure data collection on NPA clients. You can set up an NPA Data Points profile at the DO and PO level as follows:
- In your UEM console, open the Device Configuration Profile that is associated with your target devices, and then on the middle navigation menu, click Properties. The Device Configuration Policy Properties page opens.
- On the Properties page, in the Settings list, click Configured. The OEMConfig page for the Device Configuration Policy opens.
- On the OEMConfig page, next to NPA Data Points policy, click Configure. The NPA Data Points profile page opens.
- In the Profile name field, enter an appropriate name for your new Data Points profile.
- Next to NPA Data Points, click Configure. The NPA Data Points page opens.
- Depending upon your needs, use the fields on this page to enable collection of various data points. Refer to your NPA client's documentation for more details on each of these values.
- Click OK to save this new NPA Data Points profile.
The next step is to apply this profile to your target devices.
Deploy selected NPA Data Points profile to devices
To apply this new NPA Data Points profile to your managed devices, do as follows:
- In your UEM console, open the Device Configuration Profile that is associated with your target devices, and then on the middle navigation menu, click Properties. The Device Configuration Policy Properties page opens.
- On the Properties page, in the Settings list, click Configured. The OEMConfig page for the Device Configuration Policy opens.
-
Associate the NPA Data Points policy with your devices as follows:
- For DO devices, next to the Device-wide policies (Device Owner) field, click Configure. Continue to the next step.
- For PO devices, next to the Work profile policies (Profile Owner) field, click Configure.
- On the page that opens, next to the Network Platform Analytics (NPA) field, click Configure. The Network Platform Analytics (NPA) page opens.
- In the Enable NPA controls field, click True.
- In the NPA client list, select your NPA client.
- In the NPA Profile for Data Points field, enter the name of the NPA Data Points profile you created earlier.
- Click OK.
- Depending upon the settings you've chosen for deploying Device Configuration Policy changes, these changes are deployed on all the devices that use this Device Configuration Policy.