Phished
Phished can be a training source for User training: XFA warns or blocks people at sign-in who haven't finished their security training in Phished. Phished as a training source is in beta, and not every organization sees it yet. User training comes with the Max and Enterprise plans.
Phished covers security training only. It can't answer the Compliance policies accepted check.
User training
Before you start
- A Phished account with an active plan, which Phished requires for API access.
- Sign-in checks set up in XFA.
What XFA reads from Phished
XFA finds each person in Phished by the email they sign in with. It reads only:
- Whether their security training is done
- The due date
- Whether they are still active in Phished
It never reads scores or training names, and it changes nothing in Phished.
Connect Phished
- In the XFA dashboard, open User training. Under Training sources, click Add source and choose Phished.
- In Phished, open Organisation → Tokens and create a token that can only read people and reports (
recipients:read,reports:read). Phished's guide has the steps. - Copy the token. Phished shows it only once.
- Paste it under Token in the dialog and click Connect. Paste only the token, without the word "Bearer" in front.
XFA checks the token with Phished right away:
- Phished accepts it: the connection is saved and shows Connected.
- Phished refuses it, or it doesn't look like a Phished token: nothing is saved. Copy it again, or make a new token.
- The token can't read people and reports: nothing is saved. Make a token that can read them.
- Phished doesn't answer in time: the connection is saved and shows Couldn't reach Phished yet. XFA tries again at the next sign-in that uses the check.
XFA stores the token encrypted and never shows it again. To change it, open the connection and click Replace the token.
To remove the connection, open it and click Remove. While a policy still uses it, XFA refuses: click See policies and remove it from those policies first.
Next, turn on the Security training check in a policy and make sure Phished is ticked under Training source. The User training guide has what each connection status means and what people see at sign-in. On their card, Open Phished opens Phished Academy, where they sign in and do their training.
Phished-specific notes
- Not done yet: training that isn't done and whose due date is still ahead shows as due soon.
- Overdue: training past its due date, expired in Phished, or not done without a due date.
- No training assigned in Phished: the person counts as done.
- Person not found in Phished, or no longer active there: At sign-in they see nothing about training and are never blocked by it; in Sign-in Activity the sign-in shows Training not checked. XFA remembers a done or "not found" answer for up to 10 minutes, so for a person just added to Phished the check can take up to 10 minutes to start.
- Compliance policies accepted: never reads from Phished. It needs a source that has compliance policies, such as Vanta.