Office 365 SMTP open relay / office machines send encrypted email

%3CLINGO-SUB%20id%3D%22lingo-sub-2299351%22%20slang%3D%22en-US%22%3EOffice%20365%20SMTP%20open%20relay%20%2F%20office%20machines%20send%20encrypted%20email%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2299351%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20Office%20365%20Enterprise%20customers.%20I%20have%20setup%20an%20open%20relay%20SMTP%20connector%20through%20our%20365%20Exchange%20Online%20service%2C%20for%20use%20by%20our%20internal%20office%20machines%20to%20be%20able%20to%20scan-to-email%20documents%20to%20both%20internal%20and%20external%20entities.%20I%20also%20setup%20a%20compliance%20policy%20that%20automatically%20encrypts%20outbound%20emails%20containing%20credit%20card%20information.%20Our%20industry%20is%20a%20bit%20ancient%20in%20that%20many%20of%20our%20customers%20and%20vendors%20still%20rely%20on%20sharing%20credit%20card%20information%20via%20email%20message%20bodies%20or%20PDF%20attachments.%20The%20compliance%20policy%20works%20excellent%20for%20this%2C%20it%20does%20not%20require%20our%20employees%20to%20specifically%20select%20email%20encryption.%20However%20I%20have%20noticed%20that%20the%20open%20relay%20connector%20does%20not%20integrate%20with%20this%20compliance%20policy.%20Am%20I%20missing%20something%20or%20is%20there%20no%20way%20to%20automatically%20encrypt%20these%20scant-to-emails%3F%20Even%20if%20I%20have%20our%20employees%20scan-to-email%20them%20to%20their%20own%20mailboxes%20so%20that%20they%20can%20then%20forward%20the%20emails%2Fattachments%20to%20the%20external%20recipient%20using%20manual%20encryption%20the%20emails%20still%20travel%20through%20365%20unencrypted.%20This%20is%20not%20only%20unacceptable%20from%20an%20enterprise%20standpoint%2C%20it%20is%20a%20violation%20of%20PCI-DSS%20requirements.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20are%20other%20options%20for%20365%20customers%20to%20ensure%20these%20emails%20are%20encrypted%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2299351%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EExchange%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Occasional Visitor

We are Office 365 Enterprise customers. I have setup an open relay SMTP connector through our 365 Exchange Online service, for use by our internal office machines to be able to scan-to-email documents to both internal and external entities. I also setup a compliance policy that automatically encrypts outbound emails containing credit card information. Our industry is a bit ancient in that many of our customers and vendors still rely on sharing credit card information via email message bodies or PDF attachments. The compliance policy works excellent for this, it does not require our employees to specifically select email encryption. However I have noticed that the open relay connector does not integrate with this compliance policy. Am I missing something or is there no way to automatically encrypt these scant-to-emails? Even if I have our employees scan-to-email them to their own mailboxes so that they can then forward the emails/attachments to the external recipient using manual encryption the emails still travel through 365 unencrypted. This is not only unacceptable from an enterprise standpoint, it is a violation of PCI-DSS requirements.

 

What are other options for 365 customers to ensure these emails are encrypted?

 

0 Replies