![]() Let’s have a closer look: Alternatives to Email Up until today, numerous ‘secure’ alternatives have been introduced to the market to address the data privacy and complexity implications of the above scenario, but do they solve the ‘spaghetti’ problem? Figure 1 – Legacy File Transfer: Unsorted Spaghetti Landscape This situation is represented in Figure 1. NB: using FTPS only secures the spaghetti situation. ![]() FTP meanwhile requires technical knowledge to both configure and maintain by way of having to write / manage a vast spaghetti style landscape of scripts (to address the lack of functionality in the protocol that was invented in the 1970’s). ![]() is unencrypted and is therefore highly susceptible to intervention. The problem with email is that everything is sent ‘in the clear’, i.e. FTP (File Transfer Protocol) for the automated exchange of large files with unstructured data between systems (and people) – still in use today.Email for ‘ad-hoc’ transfer of files between people – frequently used today.Historically, when it came to investing in the digitalization of business processes to exchange information both behind and beyond the firewall, companies had the following options: ![]() Are you using email or FTP for transferring files containing sensitive data or Personally Identifiable Information (PII)? If you are, we encourage you to STOP what you are doing and take stock of your situation, as you could be contravening GDPR and other regulations.
0 Comments
Leave a Reply. |