Blog Security
«Why can Ana see that?» is a question your HR software should answer
Anybody who has administered SuccessFactors knows the screen. Everybody else has spent an afternoon clicking through roles trying to work out where a permission came from.
Roles add up, and that is the whole problem
Permissions look simple until somebody holds two roles. A project manager who is also on the finance rota holds both roles, and what they can actually do is the union of the two — a set that exists nowhere on any screen, because each role page only shows its own half.
So the question people actually ask — «why can Ana see the cost figures?» — cannot be answered by looking at roles. It can only be answered by resolving the sum for Ana, which is exactly what the application does internally on every page load and exactly what it usually refuses to show you.
What a useful report contains
SAP calls its version RBP troubleshooting, which is an ugly name for a genuinely good idea. Whatever it is called, three views cover the real questions, and they are different enough that one table cannot do all three.
- A matrix. One row per person, one column per permission. This is how you find the single «no» that explains a support ticket. It is also the view that does not fit on a screen, which is why it has to leave the product as a file.
- A long list. One line per person, resource and action. This is the one you filter and paste into an email, and the one an auditor wants.
- The roles themselves. What each role grants, and how many people hold it. The matrix says what somebody can do; this says why.
It has to be computed the same way the app decides
One implementation detail is worth more than the rest of the feature: the report must ask the same code the application asks when it decides whether to render a button. If the report recalculates permissions its own way, it will eventually disagree with the product — and a report that says one thing while the software does another is worse than having no report at all.
And it should be a real spreadsheet
A CSV is fine for most exports. This one is not most exports: it is a matrix a hundred and thirty columns wide that somebody has to scan looking for a wrong value. In CSV that means opening it, arguing with the separator, freezing the header row, widening the first column and adding filters — every single time.
An .xlsx arrives with the header frozen, the filters on and the columns sized. It is a small thing that decides whether the report gets used or reinvented in a spreadsheet once a quarter.
The report itself is sensitive, so it sits behind its own permission: knowing exactly what everybody in the company can do is precisely the map you would want before doing something you should not.
Frequently asked questions
Is this the same as an audit log?
No, and you want both. An audit log says what happened. A permission report says what could happen. The first is for investigating; the second is for preventing.
How often should we look at it?
When somebody joins or changes job, when a role is edited, and once before any external audit. Most teams also find something surprising the first time they ever run it.
All of this is built into Fichaloto. See how it works.
Keep reading
Security
The access list nobody maintains and everybody needs
The uncomfortable question is not what they had access to. It is how they could still get back in, and almost nobody can answer that with confidence.
Security
Access that never expires is access still live three years later
Nobody decides to grant access forever. They just do not set a date, which is the same thing under another name.
Security
Five fields, written at the moment you grant it
Recording access takes thirty seconds when you grant it and an afternoon when you try to remember it.