Glossary · Process, permissions, and security
What is an audit log?
An audit log, also called an access log, is the ordered record of actions in a system, showing who did what to which record and when. Views, changes, downloads, and deletions all go into it. A good log is protected so that entries cannot be altered afterwards.
Last updated: · Author: Şevket Erer, Co-founder, AI Specialist
What is an audit log for?
When a customer record is deleted, a price is changed, or a contract file is downloaded, the first question is who did it. An audit log leaves the answer to the record instead of to people's memory. Whether it was a mistake, an overreach, or routine work can be read from the log. A log also deters. Users who know their actions are recorded take more care. Unusual activity, such as a sign-in from a new device or repeated failed sign-in attempts, also shows up in it.
What does an audit log record?
An audit log records four facts for each action: who did it and from which device, when it happened, what was done, such as viewing, changing, downloading or a permission change, and on which record, file or setting. A good log is protected against later changes, kept for a set period, and has limited access.
- Who
The user who acted and, where known, the device they used.
- When
The date and time of the action.
- What
Viewing, creating, changing, downloading, deleting, or changing permissions; for changes, the value before and after.
- Where
Which record, file, or setting was affected.
- Protection
A good log is protected against later alteration, kept for a set period, and open to few people.
An example
At a distributor, a dealer's discount rate changed mid-month and invoices went out too low. The audit log shows which user made the change and on which day. The user says the sales manager asked for it verbally. The next step follows from that: discount changes are put behind an approval chain.
This page is general information, not legal advice; the regulations were last checked on 23 September 2026. Official text: Personal Data Protection Law (mevzuat.gov.tr), Personal Data Protection Authority (kvkk.gov.tr)
How it looks in Corex360
Corex360 Security logs every sign-in, device, and access and reports unusual events to the account owner. In Corex Drive, every view and download is logged. A permission change needs a manager's approval and is logged. Every approval is logged with who gave it, when, and from which device.
Terms often confused with it
| Role-based access control | Access control works before the action and decides who can do what. An audit log works after it and shows what was done. |
|---|---|
| Encrypted backup | A backup is a copy of the data and brings lost data back. An audit log holds the actions taken on the data; a backup cannot tell you who deleted a record. |
Related terms: Role-based access control, Data processing agreement (DPA), Encrypted backup
FAQ
How long should an audit log be kept?
There is no single answer. Regulations, contracts, and the company's own risk decide it together, and the period should be written into a policy.
Who should be able to see the audit log?
Only authorised roles, usually management and whoever is responsible for information security. Anyone who can read the log should not be able to delete it.
Is an audit log needed for data protection?
Being able to show who accessed personal data is expected as part of data security measures. When a breach is suspected, the audit log is the first place that shows what was seen, when, and by whom.
Was this page useful?