Cybersecurity

U.S. SSA EIESR v8.0

SSA EIESR v8.0 framework badge
Summarize with
ClaudeChatGPTPerplexityGoogle AI Mode
In this article
At a Glance
SSA Electronic Information Exchange Security Requirements and Procedures for State and Local Agencies (TSSR), Version 8.50
  • Classification
    Category
    Cybersecurity
    Domain
    Cybersecurity
    Framework Family
    Other
  • Regulatory Context
    Type
    Standard
    Legal Instrument
    Standard
    Sector
    Government Sector
    Industry
    Government & Public Sector
  • Region / Publisher
    Region
    North America
    Region Detail
    United States
    Publisher
    Social Security Administration, Office of Information Security
  • Versioning
    Version
    Version 8.50 (October 10, 2019); v8.0 was the June 21, 2018 draft
    Effective Date
    October 10, 2019 (Version 8.50)
    Issue Date
    October 10, 2019 (Version 8.50)
  • Adoption
    Adoption Model
    Regulatory Compliance
    Implementation Complexity
    High
  • Official Reference
License Information

License included / downloadable: Yes

The TSSR is a U.S. government document that SSA distributes to its exchange partners through the data exchange agreements; a partner-hosted copy of Version 8.50 is publicly available from the Illinois Department of Healthcare and Family Services, and the platform links to SSA's data exchange security page.

Framework text is licensed by its publisher and is included only where stated above.

Official Resources
SSA TSSR Version 8.50 (October 10, 2019), partner-hosted copy
The Electronic Information Exchange Security Requirements and Procedures for State and Local Agencies (TSSR) v8.50, as hosted by the Illinois Department of Healthcare and Family Services, an SSA data exchange partner; ssa.gov blocks automated fetchers.
Key takeaways
  • SSA's Electronic Information Exchange Security Requirements (TSSR) set the controls state and local agencies must meet to receive SSA data.
  • The current edition is Version 8.50 of October 10, 2019; v8.0 was the June 21, 2018 draft, and all previous versions are obsolete.
  • Its requirements mirror the NIST SP 800-53 management, operational, and technical controls under FISMA.
  • The TSSR is incorporated by reference in the Computer Matching and Privacy Protection Act agreements and Information Exchange Agreements states sign.
  • SSA will not allow transactions to begin until the security questionnaire is approved and both certification phases are satisfied.

Overview

The Electronic Information Exchange Security Requirements and Procedures for State and Local Agencies Exchanging Electronic Information with the Social Security Administration is known throughout its own text as the Technical Systems Security Requirements (TSSR). It is the Social Security Administration document that every Electronic Information Exchange Partner (EIEP), meaning a state or local agency with a data exchange agreement with SSA, must meet to receive SSA-provided information. The page name's v8.0 was the draft of June 21, 2018; the current readable edition is Version 8.50 of October 10, 2019, which states that all previous versions are superseded and obsolete, and SSA maintains the TSSR as a living document.

Section 1 gives the document two objectives: to let SSA certify EIEPs as compliant with its security standards, requirements and procedures, and to ensure that EIEPs adequately safeguard the electronic information SSA provides. Its primary statutory authority is FISMA as amended by the Federal Information Security Modernization Act of 2014 (Pub. L. 113-283), and unless otherwise stated SSA's requirements mirror the NIST-defined management, operational and technical controls, with each section 5 heading naming the NIST SP 800-53 rev. 4 control family it draws on. The TSSR is incorporated by reference in the Computer Matching and Privacy Protection Act (CMPPA) agreements and Information Exchange Agreements (IEAs) that states sign.

An EIEP meets the TSSR by documenting its controls in the Security Evaluation Questionnaire (SEQ), passing SSA's two-phase security certification before it gains online access (section 6.1), implementing the section 5 requirements from system access control and the automated audit trail to incident reporting, training and data center security, and taking part in SSA's compliance reviews, which section 3 calls triennial and section 6.4 describes as following a 3 to 5 year periodic schedule, with ad hoc reviews after a platform change, a TSSR violation or an unauthorized disclosure.

Why does it matter?

Access to SSA-provided information is conditional: section 1 states that an EIEP must comply with SSA's most current TSSR to gain electronic access under a data exchange agreement, and section 6 says SSA will not allow transactions to begin until the SEQ is approved and both certification phases are satisfied. Section 3 gives the SSA Office of Information Security exclusive authority to conduct and close initial security certifications and compliance reviews, with Regional Data Exchange Coordinators as the bridge to state agencies and the first point of contact when SSA-provided information is lost. The one-hour escalation in section 5.9 and the agency's duty to absorb notification costs after a breach make it a concrete obligation.

Key benefits include:

  • A named gate before access (section 6)

SSA certifies an EIEP in two phases, the SEQ and an onsite certification review, before online access to SSA-provided information begins, and a new SEQ is needed for a new platform or after SSA revokes an approval.

  • Audit trail with no exceptions (section 5.4)

A fully automated audit trail system must record every query of and every view of SSA-provided information, with user, workstation, action, business purpose and timestamp, each entry stored as a separate record.

  • A one-hour incident clock (section 5.9)

A suspected breach or loss of SSA-provided information goes to the state official responsible for systems security, who notifies the SSA contacts in the agreement; if that cannot be done within one hour, the National Network Service Center is called.

  • Named roles on both sides (section 3)

SSA's Office of Information Security, Regional Data Exchange Coordinators and the state official responsible for systems security named in the agreement carry the certification, review and reporting duties.

  • Contractors and cloud providers covered (sections 5.11, 5.12)

EIEP contractors and agents are bound to the same requirements, and cloud service providers holding SSA-provided information are addressed under NIST SP 800-144 to 800-146 and OMB M-14-03.

How does it work?

Section 4 sets general systems security standards: intent, oversight of processing under the EIEP's immediate control, a schedule, data transmission, data protection, incident response, security awareness, contingency planning and the Interconnection Security Agreement added in v8.1 from NIST SP 800-47. Section 5 lists the requirements by topic, each headed by the NIST SP 800-53 rev. 4 family it mirrors: 5.2 general system security design and operating environment; 5.3 system access control, including need-to-know access, designated authorizing officials, removal of access after adverse action, remote access conditions and identification and authentication; 5.4 the automated audit trail system; 5.5 personally identifiable information; 5.6 monitoring and anomaly detection, with a risk assessment policy, an independent assessment function, vulnerability scanning and remediation.

Sections 5.7 to 5.13 continue the list: 5.7 management oversight and quality assurance, including user ID login exception reports and inquiry match exception reports; 5.8 data and communications security; 5.9 incident reporting, with written procedures, the escalation chain described above and the EIEP's agreement to absorb notification costs when SSA requires notice to individuals; 5.10 security awareness training and employee sanctions for all employees, contractors and agents who access SSA-provided information, covering the sensitivity of the information, the Privacy Act and the rules of behavior; 5.11 contractors of EIEPs; 5.12 cloud service providers; and 5.13 a physical and environmental protection policy and procedures for data centers holding SSA data, added in v8.50 with testing requirements.

Section 6 separates two programs. The security certification program (6.1 to 6.3) is episodic: Phase 1 is the SEQ, a written plan of the EIEP's management, operational and technical controls, required for new access, a new platform, changes since the last approved SEQ or a new approval after revocation (6.2.1); Phase 2 is SSA's onsite certification review. The compliance review program (6.4, 6.5) is cyclical: EIEPs resubmit the SEQ on an agreed timeline, SSA verifies that the safeguards work, reviews follow a 3 to 5 year schedule in practice, and an ad hoc review can follow a platform change, a TSSR violation or an unauthorized disclosure. Sections 7 to 9 add definitions, regulatory references and SSA's own frequently asked questions.

Key Elements

  • EIEP and SSA-provided information (sections 1, 2)

An Electronic Information Exchange Partner is an entity with an electronic information exchange agreement with SSA; the agreements use the terms state agency, contractor(s) and agent(s).

  • Security Evaluation Questionnaire (section 6.2)

The written plan of controls SSA approves before access and reviews on a cycle; required for new exchanges, new platforms, material changes and after revocation.

  • System access control (section 5.3)

Need-to-know access designated by named officials, prompt removal after adverse action, controlled remote access, and identification and authentication of every user.

  • Automated audit trail system (section 5.4)

Separate, retrievable records of every query and every view of SSA-provided information, including read-only views, with user, device, action, purpose and time.

  • Incident reporting and costs (section 5.9)

Written procedures; notice through the state systems security official to the SSA contacts within one hour, then the National Network Service Center; the EIEP bears notification and remediation costs.

  • Certification and compliance reviews (sections 3, 6)

Two-phase certification before access; triennial or 3 to 5 year compliance reviews run exclusively by SSA's Office of Information Security, plus ad hoc reviews.

What does it cover?

The TSSR applies to every EIEP, that is, every state or local agency, with its contractors and agents, that processes, maintains, transmits or stores SSA-provided information under a CMPPA agreement or Information Exchange Agreement, for both online and batch access (section 6). It covers the systems, networks, data centers, cloud services and people involved in the exchange, and sections 5.11 and 5.12 extend it to the EIEP's contractors and cloud service providers. It does not govern SSA's own systems, and the last four digits of the SSN provided for Help America Vote Act purposes are not treated as PII (section 3). Federal Tax Information received through SSA carries additional restrictions noted in section 3.

What are its objectives?

Section 1 states the document's objective as twofold: to ensure that SSA can properly certify EIEPs as compliant with SSA security standards, requirements and procedures, and to ensure that EIEPs adequately safeguard electronic information provided to them by SSA.

Specify the minimally acceptable levels of security standards and controls to protect SSA-provided information (section 1).

Give EIEPs the criteria SSA uses when evaluating and certifying the system design and security features used for electronic access (section 1).

Set the framework and general procedures for SSA's Security Certification and Compliance Review Programs (sections 1 and 6).

Mirror the NIST-defined management, operational and technical controls so that FISMA obligations flow through to state and local partners (section 1).

Make breach notification, cost responsibility, training and sanctions explicit conditions of the exchange agreement (sections 5.9 and 5.10).

Framework in Context

The TSSR is SSA's implementation of FISMA for data it shares outward: its section headings cite the NIST SP 800-53 rev. 4 families, its Interconnection Security Agreement follows NIST SP 800-47, the SEQ serves as the NIST SP 800-18 system security plan, and section 8 lists FIPS, HSPD-12, OMB Circulars A-123 and A-130, three OMB memoranda and the Privacy Act. State agencies exchanging data with SSA for Medicaid and other benefit programs usually also run the HIPAA Security Rule, and cloud deployments bring FedRAMP into section 5.12, so one control set can serve the SEQ and those regimes. The document itself is the only source of the SSA-specific items: the SEQ, the audit trail rule and the one-hour escalation.

Common Framework Mappings

The TSSR is mapped to the federal and general security frameworks state agencies already operate, so that SEQ answers, audit evidence and incident procedures serve SSA's certification and compliance reviews and the agency's other obligations.

Mapped frameworks include:

CIS Controls v8.1

FedRAMP Rev. 5

HIPAA (NIST SP 800-66 Rev. 2)

ISO 27001:2022

ISO 27002:2022

NIST CSF 2.0

NIST 800-53 Rev.5

SOC 2

SMARTSUITE

How SmartSuite Supports the SSA TSSR

SmartSuite provides the system for managing controls, evidence, mappings, assessments, and reporting.

Use Compliance Management to hold TSSR sections 4 to 6 as requirements mapped to the SEQ answers that evidence them, with the state official responsible for systems security as owner, the section 5.9 incident workflow built around the one-hour escalation, section 5.10 training and sanctions records, and the contractors and cloud providers of sections 5.11 and 5.12 tracked in Third Party Risk Management ahead of each certification or compliance review.

TSSR Requirement Library

Load sections 5.2 to 5.13 and section 6 as requirements with owners, implementation status and the NIST SP 800-53 family each heading cites, linked to policies and evidence.

SEQ Preparation and Versioning

Draft, review and version the Security Evaluation Questionnaire against the 6.2.1 triggers (new access, new platform, changes since the last approval, revocation) and keep every submitted version with SSA's approval.

Access Authorization Records

Record who is designated to authorize access to SSA-provided information, each user's need-to-know basis, removals after adverse action and remote access approvals under section 5.3.

Incident Reporting Workflow

Route a suspected breach or loss of SSA-provided information to the state systems security official with the one-hour escalation to the SSA contacts or the National Network Service Center, the agreement's worksheet and the follow-up updates section 5.9 requires.

Training and Sanctions Evidence

Track section 5.10 security awareness training and acknowledgments for every employee, contractor and agent with access, and the sanctions applied for misuse such as employee browsing.

Compliance Review Readiness

Schedule the triennial or 3 to 5 year compliance review and any ad hoc review trigger, assemble the SEQ, audit trail samples, exception reports and data center evidence, and track findings to closure in Internal Audit Management.

Related frameworks

CIS Controls v8.1

CIS Controls v8.1 is a prioritized set of 18 Controls and 153 Safeguards, in three Implementation Groups, with a new Govern function.

FedRAMP Rev. 5

FedRAMP Rev5 is the legacy FedRAMP certification type: NIST SP 800-53 Rev. 5 baselines, 3PAO assessment and agency authorization for cloud services used by U.S. agencies.

ISO 27001:2022

ISO/IEC 27001:2022 specifies requirements for an information security management system: Clauses 4 to 10, risk treatment, the Statement of Applicability and 93 Annex A controls.

ISO 27002:2022

ISO/IEC 27002:2022 is the reference set of 93 information security controls in four themes, with attributes and implementation guidance, that supports an ISO/IEC 27001 ISMS.

NIST CSF 2.0

NIST CSF 2.0 (CSWP 29, February 26, 2024) is the voluntary cybersecurity framework with six Functions including Govern, 22 Categories, 106 Subcategories, Profiles and Tiers.

NIST 800-53 Rev.5

NIST SP 800-53 Rev. 5 is the NIST catalog of security and privacy controls in 20 families, mandatory for federal systems under OMB A-130 and FISMA; Release 5.2.0 issued August 27, 2025.

SOC 2

SOC 2 is the AICPA examination, under AT-C 105 and 205, of a service organization's controls against the 2017 Trust Services Criteria, issued as a type 1 or type 2 attestation report.

FAQ

Frequently Asked Questions For U.S. SSA EIESR v8.0 (Electronic Information Exchange Security Requirements)

The Technical Systems Security Requirements is SSA's name for the Electronic Information Exchange Security Requirements and Procedures for State and Local Agencies Exchanging Electronic Information with the Social Security Administration. Version 8.0 was a draft completed on June 21, 2018; the revision history shows 8.1 in November 2018, 8.20 in January 2019 and Version 8.50 on October 10, 2019, whose cover note says all previous versions are superseded and obsolete. SSA describes the TSSR as a living document, so partners should confirm the current edition with their Regional Data Exchange Coordinator.

Every Electronic Information Exchange Partner, meaning a state or local agency that has a Computer Matching and Privacy Protection Act agreement or Information Exchange Agreement with SSA, together with the contractors and agents that process, maintain, transmit or store SSA-provided information on its behalf (sections 1, 3, 5.11). Section 1 states that an EIEP must comply with SSA's most current TSSR to gain electronic access, and section 6 applies the compliance review program to both online and batch access.

Section 6.1 describes a two-phase security certification for EIEPs seeking online access: Phase 1 is the Security Evaluation Questionnaire, a formal written plan of the agency's management, operational and technical controls, and Phase 2 is SSA's onsite certification review; SSA does not allow transactions to start until both are satisfied. Section 6.4 describes the compliance review program, in which the SEQ is resubmitted on an agreed timeline and SSA verifies the safeguards; section 3 calls these reviews triennial and section 6.4 says SSA attempts to follow a 3 to 5 year schedule, with ad hoc reviews after a platform change, a TSSR violation or an unauthorized disclosure.

Section 5.4 requires a fully automated audit trail system capable of creating, storing, protecting and retrieving records that identify the individual user who initiates a request for or accesses SSA-provided information, with date and time stamps, the device or workstation, the action and the business purpose, each entry stored as a separate record. The system must record read-only views and access events that do not change data; the document states that all viewing of SSA-provided information requires an audit trail, with no exceptions.

Under section 5.9 an agency that experiences or suspects a breach or loss of PII or a security incident involving SSA-provided information notifies the state official responsible for systems security designated in the agreement, who notifies the SSA Regional Office contact or SSA Systems Security contact. If that cannot be done within one hour, the official reports the incident to SSA's National Network Service Center, and as a last resort to SSA's Security Operations Center. If SSA or another federal investigator decides that individuals must be notified, the agency agrees to absorb all notification and remediation costs.

Put this framework to work in SmartSuite

Manage controls, risks, evidence, and audits in one platform designed for modern governance, risk, and compliance.