Identity and access
Roles, administrative accounts, separation of responsibilities and least privilege.
We explain how we approach deployment, access, data, backups and product evolution. The exact security scope is always matched to the product and customer environment.
Not every product needs identical controls. Security must match the data, users, process criticality and the organisation’s infrastructure.
Roles, administrative accounts, separation of responsibilities and least privilege.
Event records and operation history where process accountability requires them.
Data minimisation, retention and party roles are defined before the system goes live.
Backups, recovery planning and tests are matched to the deployment model.
For hospitals, public bodies and organisations that require infrastructure control, solutions can be designed to operate in the customer’s own environment.
Responsibility does not end at deployment. Version evolution, fixes and configuration changes should be controlled.
Documentation depends on product and deployment. Instead of a fictional security badge, we prepare the information IT, DPO or procurement actually needs.
Components, flows and dependencies for the specific deployment.
Users, roles, access, backup, updates and responsibility points.
Data scope, party roles, retention and areas that may require DPA or DPIA work.
NIS2, GDPR, WCAG and sector requirements cover the entire organisation, its processes and infrastructure. JNL products can support selected controls and processes, but compliance depends on the full deployment context.