Tijd besparen op de ICT/Security afdeling!?

Frustrated Security Officer

Over the past week we have spoken to many companies that have a serious problem with staffing in the ICT/Security department. Too few employees and too many questions and problems are the cause. Most problems arise from human error and often originate with e-mail. Below is an overview of the time taken by one incorrectly sent e-mail.

Time investment in the event of a data breach due to improperly sent e-mail

  1. Direct investigation (incident investigation)
    • Ranging from several hours to even several days, depending on the sensitivity of the data and whether the recipient(s) opened the message, forwarded it, etc.
    • Usually coordination is needed between the IT department, the data protection officer (FG) / privacy officer, legal department and sometimes external (security) specialists.
  2. Communication and reporting
    • If necessary, affected individuals should also be informed (this may require additional time and coordination).
  3. Internal monitoring and measures
    • Updates in protocols, training/awareness for employees, modification of technical security measures, etc.
    • This can range from a few extra hours of work (adjustments in procedures, training) to several working days if new tools or processes need to be implemented.

Average estimate: In practice, several FGs/privacy experts indicate that, for an average company, you can easily spend 20 to 40 hours of internal time investigating, reporting, consulting and communicating around one mis-sent e-mail. In larger organizations (where more departments and stakeholders are involved), this can add up to several weeks, especially if highly sensitive data (e.g., medical or financial data) is involved.

Rather not via email

Therefore, in many cases, it is preferable not to send sensitive files via regular e-mail at all. That’s because e-mail by its very nature is not designed with the highest security standards in mind. A document that inadvertently lands in the wrong inbox can lead directly to reputational damage, loss of customer trust and time-consuming internal handling. Consider investigating the extent of the leak, notifying affected individuals, and preparing official notifications to the AP.

Especially in sectors such as healthcare, finance and government, where confidential data is involved, the risks are high. If the data is extremely sensitive, such a data breach can cost much more time and money. Moreover, these incidents are often accompanied by strict oversight or additional scrutiny from regulators.

Fortunately, there are ways to mitigate these risks. For example, Msafe offers a secure solution for sharing documents without having to include them as attachments in your mail. This is because with Msafe, files are securely stored in an encrypted environment and recipients receive a secure link and an SMS. This allows you to set exactly who has access and for how long, and limits the risk of human error.

Minimize risk and save time

  • Do not send sensitive files via regular e-mail: the risk of data leakage is too high.
  • Careless mail use costs time, money and reputation: a data breach can quickly require 20 to 40 hours of internal investigation.
  • Msafe minimizes these risks: by sharing confidential documents via a secure platform instead of sending them as loose attachments.

Want to learn more about how Msafe helps your organization with secure file management and preventing data breaches? Then feel free to contact us or request a no-obligation demo.

Share:

More Posts

KPMG-onderzoek- waarom compliance in 2026 vraagt om Secure File Sharing
Blog

KPMG-onderzoek: waarom compliance in 2026 vraagt om Secure File Sharing

Waarom is een Secure File Sharing oplossing niet meer weg te denken in een goed Compliance beleid? KPMG zegt in essentie dat organisaties te maken krijgen met meer compliance-druk, hogere eisen aan privacy en cybersecurity, en een groeiende behoefte aan monitoring, rapportage en controle. Onze Msafe Secure File Transfer oplossing is perfect voor een omgeving waarin gevoelige bestanden versleuteld, toegangsgecontroleerd en volledig traceerbaar worden uitgewisseld.

Read More »
Secure file sharing automatiseren met de Msafe API
Blog

Secure file sharing automatiseren met de Msafe API

Steeds meer organisaties willen het delen van bestanden automatiseren. Niet langer handmatig uploaden, versturen en opslaan, maar secure file sharing direct integreren in bestaande processen en systemen. Met de API van Msafe wordt dat mogelijk. Via een API kunnen applicaties automatisch bestanden uploaden, delen en koppelen aan interne systemen zoals CRM- of documentmanagementsystemen.

Read More »
Kan de US zomaar bij Msafe data
Blog

Kan de US zomaar bij Msafe data?

Uw data staat bij Msafe op Microsoft Azure in Nederland, met Microsoft Ireland als contractpartij. Toch horen we vaak de vraag: kan Amerikaanse wetgeving, zoals de U.S. CLOUD Act, invloed hebben op de soevereiniteit van klantdata? In dit artikel leggen we helder uit wat de VS wel en niet kan afdwingen, waarom data‑locatie niet hetzelfde is als jurisdictie, en hoe vaak dit in de praktijk voorkomt. We laten ook zien welke maatregelen Msafe inzet om risico’s te minimaliseren: EU‑hosting, client‑side/end‑to‑end encryptie, strikte toegang met MFA en policies, en volledige audit trails. Zodat u veilig kunt delen én aantoonbaar compliant blijft.

Read More »
waarom email verouderde technologie is
Blog

Waarom email verouderde technologie is

Email is nog steeds het standaardkanaal in vrijwel elke organisatie, maar het is technisch en organisatorisch ontworpen voor een internet waar “vertrouwen” de default was. In 2026 is de realiteit anders: email is tegelijk productiviteitsrem, risicoversneller en compliance-hoofdpijndossier.

Read More »
Alternatief voor Zivver?
Blog

Alternatief voor Zivver?

Msafe Secure File Transfer is vooral een logisch alternatief voor Zivver
wanneer je bestandsuitwisseling met externen wil standaardiseren met sterke governance en EU-hosting als expliciet uitgangspunt.

Read More »