8.1.1 General User Considerations During Identity Proofing and Enrollment (was: Social Security Numbers)
All changes in this version
Title changed
Before · SP 800-63A
Social Security Numbers
After · SP 800-63A-4
SocialGeneral SecurityUser NumbersConsiderations During Identity Proofing and Enrollment
Control changed
Before · SP 800-63A
Section 4.2 requirement 13 does not permit the CSP to collect the SSN unless it is necessary for performing identity resolution, when resolution cannot be accomplished by collection of another attribute or combination of attributes. Overreliance on the SSN can contribute to misuse and place the applicant at risk of harm, such as through identity theft. Nonetheless, the SSN may achieve identity resolution for RPs in particular federal agencies that use SSNs to correlate a subscriber to existing records. Thus, this document recognizes the role of the SSN as an identifier and makes appropriate allowance for its use.
Note: Evidence requirements at the higher IALs preclude using the SSN or the Social Security Card as acceptable identity evidence.
Prior to collecting the SSN for identity proofing, organizations need to consider any legal obligation to collect the SSN, the necessity of using the SSN for interoperability with third party processes and systems, or operational requirements. Operational requirements can be demonstrated by an inability to alter systems, processes, or forms due to cost or unacceptable levels of risk. Operational necessity is not justified by ease of use or unwillingness to change.
For federal agencies, the initial requirement in Executive Order (EO) 9397 to use the SSN as a primary means of identification for individuals working for, with, or conducting business with their agency, has since been eliminated. Accordingly, EO 9397 cannot be referenced as the sole authority establishing the collection of the SSN as necessary.
Federal agencies need to review any decision to collect the SSN relative to their obligation to reduce the collection and unnecessary use of SSNs under Office of Management and Budget policy.
After · SP 800-63A-4
SectionThe 4.2following requirementusability 13considerations doesare notapplicable permitacross all steps of the CSPenrollment toprocess. collectAdditional theinformation SSNabout unlessthese itprinciples iscan necessarybe forfound performingin identitySec. resolution8.1.2, whenSec. resolution8.1.3, cannotand beSec. accomplished8.1.4.
• byTo collectionavoid ofuser anotherfrustration, attributestreamline orthe combinationidentity ofproofing attributes.and Overrelianceenrollment onprocess theand SSNmake caneach contributestep toas misuseclear and placeeasy theas applicantpossible.
• atClearly riskcommunicate ofhow harmand where to acquire technical assistance. For example, provide helpful information, such as throughlinks identityto theft.an Nonethelessonline self-service portal, thechat SSNsessions, mayand achievea identityphone resolutionnumber for RPshelp indesk particularsupport. federalIdeally, agenciessufficient thatinformation useshould SSNsbe toprovided correlateto aenable subscriberusers to existinganswer records.their Thus,own thisenrollment documentpreparation recognizesquestions thewithout roleoutside ofintervention.
• theClearly SSNexplain aswhat anpersonal identifierdata is being collected and makeswhether appropriatecollecting allowancethe fordata itsis useoptional or not.
Note:EvidenceAdditionally, requirementsprovide atinformation indicating with whom the higherdata IALswill precludebe usingshared, thewhere SSNit orwill thebe Socialstored, Securityand Cardhow asit acceptablewill identitybe evidenceprotected.Prior• toEnsure collectingthat theall SSNinformation presented is usable.
– Follow good information design practices for identityall proofinguser-facing materials (e.g., organizationsdata needcollection tonotices, considerfillable anyforms).
– legalWrite obligationmaterials toin collectplain thelanguage, SSNand avoid technical jargon. If appropriate, tailor the necessitylanguage to the literacy level of usingthe intended population. Use an active voice and a conversational style; logically sequence main points; use the SSNsame forword interoperabilityconsistently withrather thirdthan partysynonyms processesto avoid confusion; and systemsuse bullets, ornumbers, operationaland requirements.formatting Operationalwhere requirementsappropriate canto beaid demonstratedreadability.
– byConsider antext inabilitylegibility, tosuch alteras systemsfont style, processessize, orcolor, formsand duecontrast towith costthe orsurrounding unacceptablebackground. levelsThe ofhighest riskcontrast is black on white. OperationalText necessitylegibility is notimportant justifiedbecause byusers easehave different levels of usevisual oracuity. unwillingnessIllegible totext change.will
Forfederalcontribute agencies,to theuser initialcomprehension requirementerrors inor Executiveuser Orderentry errors (EOe.g., when completing fillable forms). 9397Use tosans useserif thefont SSNstyles asfor aelectronic primarymaterials meansand ofserif identificationfonts for individualspaper workingmaterials. for,When withpossible, oravoid conductingfonts businessthat withdo theirnot agency,clearly hasdistinguish sincebetween beeneasily eliminated.confusable Accordinglycharacters (e.g., EOthe 9397letter cannot“O” beand referencedthe asnumber the“0”). soleThis authorityis establishingespecially theimportant collectionfor ofconfirmation thecodes. SSNUse asa necessary.minimum
Federalagenciesfont needsize toof review12 anypoints, decisionas tolong collectas the SSNtext relativefits tothe theirdisplay.
• obligationPerform toa reduceusability theevaluation collectionfor andeach unnecessarystep usewith ofrepresentative SSNsusers. underEstablish Officerealistic ofgoals Managementand tasks and Budgetappropriate policycontexts of use for the usability evaluation.