On paper, a voucher carries its own history. You can see the signatures, the dates, the initials beside each correction and the stamp that says received. When an office moves that work into software, the history does not come along by itself. Unless the system is built to keep it, a figure can change and nobody can say who changed it, when or why.
What an audit log is
A log is a record of the events that occur within an organization's systems, made of entries that each describe one event. That is the definition used by the United States National Institute of Standards and Technology (NIST) in its guide to log management. The guide lists what logs are good for: identifying security incidents, policy violations and fraudulent activity, and supporting auditing and internal investigations.1
An audit log, sometimes called an audit trail, is the part that concerns people's actions: who signed in, who opened a record, who approved a request, who changed an amount. It is the software version of the logbook at the guard's desk and the initials on the voucher, kept automatically.
The important word is automatically. A log that depends on staff remembering to fill it in is only as complete as their memory. We think the system itself should write the record as part of doing the work, with no extra step for the user.
Why public systems need one
Accountability is already the rule for public funds. The Government Auditing Code of the Philippines, Presidential Decree No. 1445, declares that all government resources must be managed and used in accordance with law and regulations. It makes the head of each agency immediately and primarily responsible for the funds and property of that agency, and it requires that claims against government funds be supported with complete documentation.2
The same code gives the Commission on Audit (COA) authority over the examination of books, records and papers, and over the preservation of vouchers for ten years.2 A digital system that cannot show how a transaction was approved leaves the agency head answerable for something he or she cannot prove.
COA has set out how electronic records fit these rules. Its Circular No. 2021-006, dated September 6, 2021, accepts electronic documents with electronic signatures in place of signed paper, under conditions. Digital signatures must provide authentication, which links the signer to the document; integrity, which assures it was not altered; and non-repudiation, which means the signer cannot later deny having signed. Agencies must also keep their electronic records protected from unauthorized alteration or destruction.3
Those three words describe what a good audit log does for every action in a system, not only for signatures. It shows who acted, shows that the record has not been changed since, and leaves no room to deny it.
What a good log records
The Open Worldwide Application Security Project (OWASP), a nonprofit that publishes free security guidance, sums up a useful log entry in four questions: when, where, who and what.4
When is the date and time. Where is the part of the system and the address the action came from. Who is the user account. What is the type of event, the record it touched and whether the action succeeded or failed. OWASP's guidance also names the events worth recording, including sign-in successes and failures, attempts to reach something the user has no permission for, and the use of higher-risk functions such as managing user accounts or other administrator actions.4
For a government office, we think one more item belongs where it matters: the value before and the value after. Knowing that an amount was edited is useful. Knowing that it went from 15,000 to 51,000 pesos is what an auditor needs.
- When: the date and time of the action.
- Where: the screen or function, and where the request came from.
- Who: the account that acted.
- What: the action, the record affected, and the result.
A log that can be edited proves nothing
A record is only evidence if it cannot be quietly changed. NIST's guide says log management includes protecting the confidentiality, integrity and availability of logs.1 OWASP is more specific: build in tamper detection so that a changed or deleted entry can be noticed, restrict who can read the logs, and record and monitor all access to the logs themselves.4
Our approach follows from this. The people whose actions are being recorded, including administrators and including us as the developer, should not be able to rewrite the record. Corrections are made by adding a new entry that says what was corrected, the way an accountant makes a correcting entry in a ledger and does not erase the old one.
Missing logs are a recognized weakness in their own right. Security Logging and Alerting Failures is ninth on the 2025 edition of the OWASP Top 10, the list of the most critical security risks to web applications.5 Without a working log, a breach or a misuse can go unnoticed.
Keeping records without keeping too much
A log is also a collection of information about people, so it has to respect privacy. OWASP lists what should never be written into a log directly: passwords, access tokens, bank account and payment card data, and sensitive personal data.4 The log should say that a staff member opened a patient's record. It should not copy the diagnosis into the log.
The Data Privacy Act of 2012 sets the frame. Personal information must be processed in line with the principles of transparency, legitimate purpose and proportionality, and kept only for as long as necessary for the purpose it was collected for. The same law gives a person the right to reasonable access to information about how his or her data was processed.6
The two duties fit together better than they first appear. A log of who viewed a record is how an office can answer a citizen who asks who has seen their file. The balance lies in recording the action without the content, and in setting retention periods on purpose. OWASP's advice is that logs must not be destroyed before the required retention period ends and must not be kept beyond it.4
What to look for in a system
An office in the Bangsamoro that is considering any system for money, personnel, permits or beneficiaries can test this in a demonstration. Ask the supplier to change one record, then show you the history of that record: who changed it, when, and what it said before. Ask who is able to delete that history. The answer should be no one in the ordinary course of work.
Ask also whether your own auditors can read the log without the supplier's help, and how long entries are kept. A system that answers these questions well protects honest staff as much as it exposes dishonest ones, because the record shows what each person did and did not do.
Sources
- Guide to Computer Security Log Management (NIST SP 800-92). National Institute of Standards and Technology, September 2006.
- Presidential Decree No. 1445, Government Auditing Code of the Philippines. The Lawphil Project, Arellano Law Foundation, 1978-06-11.
- COA Circular No. 2021-006, Guidelines on the use of Electronic Documents, Electronic Signatures, and Digital Signatures in Government Transactions (attached to DPWH Department Memorandum Circular No. 57, series of 2021). Commission on Audit, copy published by the Department of Public Works and Highways, 2021-09-06.
- Logging Cheat Sheet. OWASP Cheat Sheet Series.
- OWASP Top 10:2025. OWASP Foundation, 2025.
- Republic Act No. 10173, Data Privacy Act of 2012. The Lawphil Project, Arellano Law Foundation, 2012-08-15.