Links last opened 28 October 2026. Record confirmed by a person on 10 October 2026. 2 recorded changes, listed below.
RSA Security contracts through RSA Security LLC, registered in United States. Its trust center is published at https://www.rsa.com/company/secure/. Its customer data processing agreement, also called a data processing addendum, is published by RSA Security itself; the link is below. Its sub-processor list is published by RSA Security itself; the link is below. We open those pages every day — last on 28 October 2026 — and a person last went through this record on 10 October 2026.
A ready row. Replace the purpose with what your client actually uses RSA Security for.
| Subprocessor | Legal entity | Country | Purpose | Transfer | DPA |
|---|---|---|---|---|---|
| RSA Security | RSA Security LLC | US | — | — | https://www.rsa.com/standard-form-agreements/ |
Changes we noticed on RSA Security's own pages, each with the page we saw it on. The vendor does not publish this, and neither does anyone else.
27 October 2026
RSA Security added Salesforce, Microsoft Azure, and other subprocessors (Close, Root, Remote) as of September 2025. These new subprocessors now process data on behalf of RSA and should be added to your records of processing and data processing agreements.
Seen on https://community.rsa.com/s/article/RSA-Subprocessor-Information
15 October 2026
We recorded a change to the sub-processor list link.
Enter your website: each service it loads, what it is for and links to its own DPA, in a minute or two. No sign-up.
Worked out from the registry and what we have written: the country this vendor contracts from, the guides that answer the question this page raises, and the rest of the registry.