Rights separation
Roles by job function instead of full access. A sales manager should not be able to export the entire client database.
We look at applications not as programs but as the places where your data sits and through which it leaves.
Roles by job function instead of full access. A sales manager should not be able to export the entire client database.
Each exchange runs under its own account with minimal rights rather than as an administrator.
Restricting access to programming interfaces by address and key, limiting the request rate.
Who changed and exported what. Without it an incident cannot be investigated.
A procedure for installing security fixes with a test environment.
Scanning the applications and reviewing the results with prioritisation.
The main work is not technical but agreeing who genuinely needs to see what.
A list of the applications, who uses them, which data they hold and where it is sent.
We agree with the department heads which roles are needed and what they include.
We configure the roles, move integrations onto separate accounts and switch on logging.
Every six months we check that the rights are still current: people change jobs while their access stays.
Rights accumulate and are almost never revoked. An employee moves from department to department, gaining new access each time, and three years later can see half the company. A regular rights review closes this without a single purchase.
It does, and they are enough for most tasks. The problem is usually not a missing mechanism but that everyone has been given the full rights role because it was simpler. Configuring roles around real duties solves the question without any additional products.
Restrict them from the outside: access to the application only from a particular network segment, only for particular users, with connection logging. That does not give full protection but it sharply narrows the surface.
For applications reachable from the internet, at least quarterly and after every major update. For internal ones, every six months. More important than the frequency is that the results are worked through rather than filed away in a report.
Tell us which systems you use. We will look at who sees what and where integrations run with excessive rights.
Request received
We can already see it. We will reply within one business day, and for urgent matters we will bring in the on-duty engineer right away.
City not found. Please check the spelling.