Uploading and storing Passport photos securely
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-16-2026 01:42 AM
Hi all, hoping for some architectural advice, I've been given a requirement where customers need to upload passport photos, so we can use that passport info to make travel bookings on their behalf. Once uploaded we would store the passport photo for 1 year, at which point we would re-request the upload from the customer.
I'm building a scoped app, with a public portal page containing a record producer. The passport image is then attached and submitted, which then lives as an attachment on the csm_consumer record (so in the sys_attachment table). ACL's would then limit the number of people who can view the image.
Is there a better approach? I'm unsure if this is secure enough, we do not have edge encryption configured and so I believe ServiceNow staff could gain access. Is there a risk with the images being stored in sys_attachment?
Thanks in advance for any advice
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-16-2026 02:38 AM
Hi OWelch,
I’d probably avoid storing the passport image directly on the csm_consumer record. It will work, but for something this sensitive I’d rather keep it separate and lock it down more strictly.
For example, you could create a custom table like x_your_app_passport_vault and store the attachment there. Add a reference back to the consumer, plus fields like upload date, retention until, status and verified. That way normal CSM access stays separate from the passport data.
I’d also create a dedicated role for the small group that really needs access and use strict ACLs on that table. On top of that, I’d check what encryption options you have available, for example KMF or attachment encryption. I would verify the exact setup with ServiceNow though, especially if the requirement is that admins or ServiceNow staff should not be able to read the image.
For the one year retention, a scheduled flow could check for expired records, delete the related attachment, set the status to pending reupload and ask the customer to upload a new passport.
I’d also ask whether the full image really needs to be stored for the whole year. If you only need a few passport details after verification, deleting the image earlier would reduce the risk quite a bit.
If this helped, could you mark it as helpful or as the solution?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
Storing the image as an attachment on the consumer record is a workable pattern. ACLs control who can read it in the application, but they do not encrypt the stored file. To protect it at rest, add attachment encryption to the table that holds it.
ServiceNow’s documentation describes two ways to do this for specific tables:
- Edge Encryption can encrypt attachments, with only Standard AES128 or AES256 allowed for attachments. It runs through the Edge Encryption proxy, and you have not configured it.
- Field Encryption Enterprise, which needs a subscription, handles both field and attachment encryption through Encrypted Field Configurations. It uses the Key Management Framework for key management. The documentation says Column Level Encryption and Column Level Encryption Enterprise are being prepared for future deprecation starting with Zurich, so avoid starting a new design on those.
To take this forward:
- Ask your ServiceNow account team whether your entitlements include Field Encryption Enterprise, and which key options it gives you.
- Put the passport attachment on a table of its own, with an encrypted field configuration for attachments and an access policy for the roles that need to see it.
- Keep the ACLs on that table tight, and test downloading the image as a user without the role.
- Raise the question about ServiceNow staff access with your account team or security contact. I did not find documentation that settles it, so get the answer in writing for your compliance team.
The one-year retention is not built in for a custom attachment. The Employee Document Management retention policies in the documentation apply to HR documents. For your scoped app, use a scheduled job that deletes the attachment after a year and triggers a new upload request. Test it in a sub-production instance with sample images first.
Sources: