Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

Something changed in my system and nobody can tell who did it

Short answer

If nobody can say who changed what, the system is probably not recording changes, or everyone uses one shared login. Check whether the tool or cloud account keeps an activity log, stop shared logins so each action has a name, and keep logs somewhere people cannot edit. Adding a trail later helps from then on, not for the past.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • A price, a stock figure or a setting changed and everyone says it was not them.
  • A customer record was edited or deleted with no explanation.
  • Several people use one login for the admin area.
  • I ask the developer who did it and the answer is that it is not recorded.
  • A client or insurer asked for activity logs and there are none.

Why does this happen?

  1. Shared logins hide the person

    If five people use one account, the log can only say that the account did it. Individual logins are the first step.

  2. Many systems record only the current value

    A simple database stores what is there now. Unless someone built a history table or an activity log, the old value is gone as soon as it is overwritten.

  3. Cloud activity is recorded, but only for a limited time unless you set more up

    AWS says CloudTrail's event history is a viewable, searchable and downloadable record of the past 90 days of management events in a Region, available automatically, and that trails and CloudTrail Lake are the ways to keep events longer.

  4. Workspace and admin tools keep logs only if someone looks

    Google's security checklist for larger businesses tells admins to review the Admin audit log to track admin tasks, and to turn on alerts for risky events such as setting changes by another admin.

  5. Logs kept next to the thing they watch can be changed

    A log stored on the same server, editable by the same people, is a weak record. Keeping a copy elsewhere makes it trustworthy.

What can I do about it today?

  1. Write down what changed and when you noticedTime, screen, record and what it looked like before, if known. This is your starting point for any search.
  2. Do not change the system again to find outExtra edits can overwrite the little history that exists. Take screenshots first.
  3. Find out which logs existAsk your developer or tool vendor whether the admin area, database, cloud account or email keeps an activity log, and how many days it holds.
  4. Stop shared loginsGive each person their own account so that every future action has a name.
  5. Download what you can todayIf a log only keeps a limited window, export it now so that it is not lost while you investigate.
  6. Avoid accusing anyone yetA log shows which account acted, not always which person was behind it.

When should I bring someone in?

  • The change cost money or affects customers.
  • You suspect someone outside the business.
  • The system has no log at all and the data matters.

How do I handle it?

  1. Find what is already recordedServer, database, application and cloud logs, and how long each is kept.
  2. Rebuild what happened from the evidenceI match the timing of the change against those logs and say what is proven and what is only likely.
  3. Add change history where it countsFor the records that matter, I add who, when, old value and new value, written in a way that does not slow the system.
  4. Keep a protected copy of the logsLogs are sent to a place that normal users and the app itself cannot edit.
  5. Give each person a loginShared accounts are replaced by named ones with only the access each person needs.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Can I see changes from before the logging started?

Usually not, unless a backup or an old export holds the earlier value. That is why saving evidence first matters.

How long are cloud logs kept?

For AWS, the event history covers the past 90 days of management events in a Region. Longer storage needs a trail or CloudTrail Lake, which have their own settings.

Does adding an audit trail slow my app?

A well-built one adds little work. I would test it on your system before turning it on in production.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.