I've noticed a lot of recommendations for SMT2GO, and after trying it out, we liked it as well. However, we have a concern as we consider replacing our internal relay. Our security team is worried about how to manage Data Loss Prevention (DLP), especially regarding potential scanning to external email addresses from copiers. They want to ensure that any documents containing Personally Identifiable Information (PII) or Protected Health Information (PHI) are flagged correctly. Is there a way to route SMT2GO through our Microsoft 365 tenant or a third-party email filter for outgoing emails to catch these DLP incidents?
3 Answers
That’s true, SMT2GO would technically be considered external. So, even if they scan internally, any PII could be an issue if routed out. It might be best to look at multi-functional printers that support OAuth and connect them with your 365 DLP systems.
Just out of curiosity, how does SMT2GO compare to a straightforward postfix relay connected to 365? Is it a significant improvement or just different?
To manage DLP, focus on file-level control. Make sure that no one can print documents with PII or PHI unless they have permission to fax. It’s important to keep sensitive information under close watch.
Exactly, but making those restrictions can be tricky in practice!
Good point! I believe our multifunction printers do support OAuth, so that could work.