This path is for the Security Monitor, the role that reads far more in portierX than it changes. The Security Monitor finds out who held which key and when, follows incidents and access reviews, and helps the Organisation Admin prepare the evidence for an audit. portier's introduction team trains the role on this path and leaves it behind as the manual. You can also work through it on your own.
Narrow the audit log to a person, a key, a door or a period, and read an entry.
Filter the report on reported incidents and export it as a file.
Follow a lost or stolen key from its report to its outcome.
Read an access review with its answers and what came of them.
Prepare your part of the evidence for an audit.
You need a portierX login to your organisation with the Security Monitor role. Your Organisation Admin gives you the role.
Your first day in portierX. You sign in for the first time and know where your work as Security Monitor begins.
Find your way around portierX. You find every area you read from, through the sidebar, the header and the command menu.
What your role lets you see and do. You know what your role shows you and which changes belong to other roles.
Show who had access and when. You answer from the audit log who did what and when.
Run and export a report. You read the incident report and take it away as a file.
What portierX can prove in an audit. You know which record answers which of an auditor's questions, and who produces it.
Report a lost, stolen or damaged key or card. You understand what a loss report sets off, down to the email you then receive.
Close out an incident. You can read how an incident ended and what its record keeps.
Access reviews: what they are and how they run. You read a review with its answers and know what each removal did.
Preparing for an audit. You know your part of the preparation and who takes on the rest.
Narrow the Audit Log to one access point, for example the door to your server room, and to the past month. Then open an entry and read its Details and Context tabs (Show who had access and when).
In the audit log, tick Show Exceptions Only, set the period to one week and bookmark the page, so the same list opens again (Show who had access and when).
Under Reports, open the Credentials with Reported Incidents report, switch All statuses to Open and choose Export CSV. The file downloads to your computer and changes nothing in portierX (Run and export a report).
Under Reviews, open a review on the Closed tab and read, row by row, who answered and what came of it. If no review is closed, take one from the Open tab (Preparing for an audit).
Which roles may export the audit log? (Show who had access and when)
Who sets how long the audit log keeps its entries? (What portierX can prove in an audit)
Until when does a credential reported stolen keep opening doors in a connected access control system? (Report a lost, stolen or damaged key or card)
Who closes out an incident once its outcome is known? (Close out an incident)
When does an access review close on its own? (Access reviews: what they are and how they run)
When you are named to decide requests or answer access reviews, continue with the path for approvers, reviewers and key holders (Training path: approvers, reviewers and key holders).
