6. Add and prioritise an Access Policy, then deploy

Use this when the concern is who can use an AI app, not what they share — blocking shadow AI, allowing Copilot only for a specific team, warning contractors before they use Claude.

Before you begin

Reading the table

The Access Policies table has these columns:

Steps

  • Priority — 1, 2, 3… (first match wins).
  • Policy Name — name and scope (e.g. Block DeepSeek, Allow Copilot – Engineering).
  • AI Application — target app.
  • Category — Shadow AI, Search AI, Enterprise AI, Coding AI, etc.
  • Users/Groups — scope (e.g. All Users, Engineering Group, Contractors Group).
  • Risk — Critical, High, Medium, Low pills.
  • Action — Block, Warn, Monitor, Allow pills.
  • Created By — System (auto-created by ARIA / Forcepoint defaults) or Manual (authored by an admin).
  • Last Modified — timestamp.
  • Status — on/off toggle per row.

Next steps

Above the table sits a yellow banner: "Control which AI applications users can access. Block shadow AI tools like DeepSeek or Perplexity, or allow sanctioned enterprise AI tools on a per-group basis."

Steps

  1. Go to AI Security → Policy and click the Access Policies tab.

  2. Click + Add Policy in the top-right of the table. Fill the form: policy name, target AI application, user/group scope, risk level, action (Allow/Warn/Monitor/Block).

  3. Save. The new policy appears at the bottom of the table with a default priority.

  4. To move it up or down, click Change Priorities above the table — this enters a reorder mode where you can drag rows. Lower-number priorities evaluate first, so Block Shadow AI rules should sit above Allow enterprise AI rules.

  5. Verify the Status toggle is on (green). Policies with the toggle off are drafts.

  6. Commit the change by clicking the yellow Deploy → button in the top-right of the page. The button turns yellow whenever there are undeployed changes in either tab; it's green or subdued when everything is live.

  7. After Deploy succeeds, return to the dashboard to confirm the new policy's impact — see How-to 9 for reading the Policy Effectiveness tab.

Edit / Delete existing rows

  • The toolbar above the table has a ✏️ edit icon and a 🗑️ delete icon that act on selected rows (use the header checkbox to select all, or per-row checkboxes to select a subset).

  • The ⋯ menu at the end of each row offers the same actions plus a quick-duplicate.

Tips

  • Every Access Policy edit parks changes in a draft until Deploy is clicked. Make several related changes, review them in one pass, then deploy as a batch.

  • Prefer narrow actions first. Monitor generates evidence before you graduate a rule to Warn or Block. ARIA on the dashboard will tell you when a rule is "stable enough" to graduate — see How-to 10.