Practical support · details
From requirements to practical tools
ChipLogin helps authenticate employees, manage their access, protect sign-in credentials and trace events. Here is how these functions support the requirements covered in the previous chapter.
1 · Personal card and personal account
ChipLogin assigns a card and destination-specific accounts to each person. Convenient card use helps introduce personal sign-in even at shared workplaces.
cryptographic card authentication uses a secret key. When presented, the card responds to a ; copying its public number alone is not enough for successful authentication. Only after this step can ChipLogin release the credentials for the relevant account.
requirements apply to the complete sign-in solution. A card is a possession factor; automatically supplying a stored password does not by itself provide a second independent factor.
2 · Keep access up to date
An administrator creates an employee record and assigns a card when the employee joins. Access is adjusted when their work changes, and a lost card is blocked. The management interface shows people, their cards and permissions for connected computers, machines and doors.
When an employee leaves, the company revokes their access in ChipLogin and disables the relevant Windows and application accounts. Open sessions must be ended in the respective system.
3 · Protect data in your own environment
Depending on the mode, credentials are stored on the workstation or the customer's . ChipLogin stores them encrypted; the network connection to Auth is protected by encryption and mutual authentication. The company keeps its sign-in infrastructure within its environment and can include in its own access, backup and recovery policies.
Licensing services and diagnostics have their own data flows. Their scope and access controls are assessed separately. This information helps position ChipLogin among the measures used to protect data under Article 32 .
4 · Evidence for reviews and incident handling
ChipLogin records card authentication, the time, the relevant identity and the result. Records also cover administrative changes, such as an access adjustment.
Card authentication and final acceptance of an account are two different steps. When investigating an event, the administrator therefore combines ChipLogin records with Windows or application logs as needed.
Records form a chain of , with reference hashes sent to a witness. This helps detect later changes to the history. The company decides who may access the records and how long to retain them.
A technical measure within your company's rules
ChipLogin supports specific aspects of security. The company assigns responsible people, access allocation rules and incident response procedures to them. During a review, it can demonstrate the link between a requirement, a configured feature and available evidence. Overall compliance results from combining these technical measures with security management across the organisation.