Employee personnel files contain TC ID number, date of birth, address, should these be stored encrypted?

we were keeping it open too.. then then we got flagged in an audit. honestly now we made it an encrypted Excel, good

In Excel: Tools → Protect Sheet, set a password. Or restrict access on Google Drive.

I agree with this. Forgotten test environments are more often the entry point than live systems.

Proven by experience.

Three different views emerged, they all complement each other. If the notification path is long, notifications don't arrive; missing notifications mean delayed incident detection.

If you have questions, write them; I'll answer as best I can.

There's a part I don't understand. The harder it is to reverse a decision, the slower you should make it.

Everything goes well for the first three months; problems arise in the fourth. That's all, sorry if I went on too long.

This thread is archived.

Following.

Correct in theory, but it doesn't work that way in practice. When you try to change everything at once, nothing settles.

This is my opinion, I'm not claiming it's absolute truth.

i disagree with you on this point. the answer varies greatly by industry; there is no one-size-fits-all rule.

everyone rushing into employee personnel file gets stuck at the same point... anyway of course it varies if your situation is different.

Let me summarize the topic, since several different answers were given. The biggest time-waster for us was not knowing who had the final say.

Security isn't absolute; it's about making attacks not worth the effort. If you post the result here, it will help others too.

I've been dealing with this for a long time. If permission and scope aren't in writing, don't start that test.

Proven by experience.

We experienced almost the exact same thing last year. When making a decision, first look at what data you have on hand.

we experienced almost the exact same thing last year. tbh if the notification path is long notifications dont arrive; missing notifications mean delayed incident detection.

if you have questions, write them; I'll answer as best I can.

Noted, thanks.

We got stuck at the same point for a while. People defend habits, not processes. Resistance comes from there.

Don't miss this: Any unwritten clause becomes a point of disagreement later, as both sides remember it differently.

Of course, it varies if your situation is different.

Same here. When you try to change everything at once nothing settles.

If you dont write this down from the start it leads to arguments later. Correct me if Im wrong.

I'm a small business, let me explain from my side. Most time waste accumulates in tasks waiting for approval.

Good luck with that.