Accountant got an email from the 'Tax Office', clicked a weird link — could the bank account have been compromised?

did he give out the bank password?? that's really bad. change everything immediately, cancel the debit card. the bank often reverses this but there's a time limit. also tell the accountant stop clicking these kinds of emails...

In phishing emails, the sender email address is usually fake. Check the mail header: Return-Path, SPF, DKIM, DMARC records. If the domain isn't verified, it's almost certainly phishing. The accountant's computer might have a keylogger, it's recommended to access the bank from another device. Check if the bank has account limits, if transaction bounds can be set.

The Tax Office never sends links via email bro... clients not reading emails is always a problem. Tell the accountant too, avoid these emails, always go directly to the site. And now what to do: check with the bank management company (Visa Mastercard), is there a fraud dept... thing for credit freeze? Yes, freeze it then unfreeze...

edit: typed from phone, sorry for typos.

Email filtering and verification mechanisms are critical in corporate environments. Recommendations: 1) Mandate SPF DKIM, DMARC authentication setup, 2) Provide email security training (phishing awareness), 3) Implement multi-factor authentication for all company accounts 4) Establish a clear channel with the bank — access the computer from a different network or switch to a phone call. 5) Conduct a risk assessment for the entire structure.

Got an email from the Tax Office yaaa 😅 Stuff like this only happens in movies of course... Interesting. Anyway the accountant wont get fired right, this is also a learning opportunity. Be more careful next time...

If youre going this route sort this out first. I mean if you dont write this down from the start, it leads to arguments later.

The real issue isnt the number, but what its based on... I mean good luck with that.

i feel the same way then solutions that work at a small scale collapse when you grow; I learned this late.

if I were you, Id go this route.

I've been down this road, let me tell you. Start with a small trial; don't commit to everything at once.

Most time waste accumulates in tasks waiting for approval.

Three different views emerged they all complement each other. If you don't write this down from the start, it leads to arguments later.

I didn't know that. Forgotten test environments are more often the entry point than live systems.

Security isn't absolute; it's about making attacks not worth the effort. Of course, it varies if your situation is different.

i was thinking the same thing. everything goes well for the first three months; problems arise in the fourth.

good luck with that.

Thanks, that was the answer I was looking for. Trying to do this alone is the most expensive way.

If I were you I'd go this route.

I didn't know that.

I've been dealing with this for a long time. Trying to do this alone is the most expensive way.

Hope this helps.

Following. The harder it is to reverse a decision, the slower you should make it.

This approach has a cost, which isn't discussed. Start with a small trial; don't commit to everything at once.

Start with a small trial; don't commit to everything at once. If you have questions, write them; I'll answer as best I can.

Three different views emerged, they all complement each other. Trying to do this alone is the most expensive way.

Good luck with that.

Thanks for writing this, that's the right way. Taking measures without an inventory leaves doors you haven't seen open.

That's all, sorry if I went on too long.