Allowing external email to update HR case records

TriWorks
Tera Contributor

We currently allow external mail to leverage a "Guest" account and generate net-new HR cases. However, there is no dialogue/email activity between the HR analyst and the submitter because we don't allow external mail to update HR records. Therefore, HR analysts have to communicate via their Outlook client and then paste these ongoing communications into the appropriate HR case.

We block external to avoid a potential flood of spam or an outright malicious attack. However, we've taken a blanket approach to this (no exceptions) and our HR department is wondering if there's a way to open restrictions such that external email addresses can update records. 
>What are the potential downsides to removing restrictions (beyond the spam concerns)?
>Is there a way to 'whitelist' an address such that it's allowed to update a record but otherwise restrictions stay in place?

Any advice or OPEX is appreciated. Thanks!

1 REPLY 1

Max Dore
ServiceNow Employee

Hi @TriWorks , 

I'd recommend a narrowly scoped exception, not removing the restriction globally. I think your key distinction is between “this address may email us” and “this sender may update this particular HR case.” So your exception should enforce both.

 

Potential downsides beyond spam

Confidentiality and identity assurance. SN explicitly identifies confidentiality and integrity risks from insecure or compromised personal mailboxes. Approving an address does not establish who currently controls that mailbox.

Unauthorized or misleading case updates. Inbound processing can identify a target record through a watermark or record number, then evaluate action conditions. Record matching should not necessarily be treated as sender authorization; I'd recommend requiring a separate check that the sender is an approved participant on the matched case. Just my recommendation for security best practice.

Weaker attribution when everyone is Guest. With automatic user creation disabled, unmatched senders run inbound actions as Guest. Consequently, Guest identity alone cannot distinguish one external correspondent from another; retain and validate the actual sender address for your exception.

Unintended processing elsewhere. Inbound email flows run before inbound actions, and an action whose conditions fail is skipped in favor of the next eligible action. A restrictive exception is therefore insufficient if another flow or action still accepts the message.

There is also a sender-authenticity concern: ServiceNow’s support guidance states that its described inbound-mail design does not automatically reject SPF failures based on SPF or DMARC policy. Do not assume an address allowlist alone provides authenticated identity; have your messaging/security team validate the controls on your actual mail route. Check KB1709711

 

Can you whitelist an address?

Yes, selective inbound handling is possible but the documented HR property itself is Boolean, not an address allowlist to my knowledge. 

 

I'd evaluate these 2 approaches:

Known external user identity: The platform matches sender addresses to active sys_user records, and an inbound action’s From field can restrict it to a selected user. Evaluate this for individually managed external identities, but do not assume creating a user automatically authorizes HR case updates. Also note that deleting or archiving the selected user removes the action’s From restriction which is a documented maintenance hazard. 

Controlled exception for external senders still using Guest: Use a dedicated inbound condition/script to check an approved address and its association with the target case. This is a proposed custom authorization design using documented inbound-action capabilities but not a documented native HR allowlist feature. Verify how it interacts with the HR restriction before implementatinng it.