Understanding Why No Policies Are Listed
An empty Data Security tab means no content inspection policies have been configured for your organization yet. Until at least one exists, AI Security records what your users do with AI applications but does not inspect what they send.
The tab reads policies from the Forcepoint Data Security portal rather than holding its own. An empty list means there is nothing there to read.
The usual reasons
- Nothing has been configured yet. The most common reason on a new tenant. No policies were switched on during the guided setup, and none have been created since.
- Setup was skipped. If Skip for Now was selected on the Data Protection step of the guided setup, no policies were activated.
- Your organization uses on-premises Data Security. AI Security reads cloud policies. If your data security is managed on-premises, this tab stays empty and the policies are maintained elsewhere.
- Policies exist against a different organization. Policies are held per organization. If they were created against one your AI Security tenant is not configured for, they do not appear here.
What an empty list means in practice
AI Security still works. It continues to record which AI applications your people use, how often, and which agents are active — that comes from the connectors, not from policies.
What it cannot do is inspect content. Nothing checks what your users are sending to AI tools, so no data security violations are raised, the Sensitive Data Exposure tab stays empty, and the violation counts on the AI Landscape widgets show zero.
Filling the list
Select Add in DLP to create a policy on the Forcepoint Data Security portal, then come back and refresh this tab. If you skipped the guided setup, you can also return to it and enable the policies it recommends for your organization.