# Presentation: 310679

## What’s In A Number? (cont.)

- First 3 digits = “area” where original application for SSN was filed -- typically the applicant’s residence
- Middle 2 digits = “group” within a State;  **High Group List **published monthly as check against errors and/or fraud
- Last 4 digits = “serial numbers”

## Will SSA Ever Run Out of Numbers?

- SSA has never issued a previously-used number
- SSA predicts that combinations of numbers will not be exhausted for 65 years

## SSA Master Database

- _Numident records:_
**SSN**
**Individual’s name**
**Mother’s maiden name**
**Father’s name (optional)**
**Date of birth**
**Place of birth**
**Gender and race (optional)**
**Citizenship**
**Internal processing codes**
**Death records**

- _Alphident records:_
**Alphabetical Index Register, cross-reference listing by last name**

## Data Verification and FPLS

- All New Hire, Quarterly Wage and Unemployment Insurance SSNs verified before placed on the NDNH (PRWORA requirement)
- States have the option of having “bad” SSN data returned to them for correction
- SSA and OCSE looking into possibility of a pilot program to return data directly to employers for corrections

## SSN Terminology

- Enumeration: assignment of the actual numbers
- Verification: process by which SSNs are checked for “authenticity”
- done through one or more EVS or Annual Wage Reporting routines
_**not**_ proof of identity of an individual

## SSN Terminology (cont.)

- Unverified: the record input does not match the record at SSA
- Nonverifiable: not enough data is available on the input record to *attempt* a match
- Multiple SSNs: One individual has more than one SSN (there are legitimate reasons for this)

## Enumeration Verification System 

- Verification: certifying that data on the incoming record matches that in SSA master database
- Verification routines: programs through which SSNs are processed to try to achieve a match (7 presently in use)
- Routine to be used and amount of information to be returned is determined by the agency requesting the data

## Enumeration Verification System (cont.)

- Child Support uses Routines 217 and 220
- Routines have “tolerances” built in to allow for “typo’s” on name or DOB
- “Single-select” routine returns *probable*  *match* of SSN where associated with exact name, DOB and sex code
- “Alpha Search” routine returns *probable* *match* based on near-spelling of name and exact DOB

## Reasons for an Unverified SSN

- Errors in payroll records/data entry
- Failure to notify SSA of name changes
- Incorrect information given to SSA
- Use of an incorrect SSN
- Errors on SSA records

## SSN Importance

- At their inception SSNs were merely a method to keep track of earnings
- SSN has become a unique identifier and is now an important element in CS cases
- The quality of the SSN in the NDNH and the FCR is key to locating NCPs
- Receiving validated SSNs from SSA has improved the Child Support Enforcement program

## Module 6: External Locate Sourcesand Future Enhancements

- Module 6: External Locate Sourcesand Future Enhancements

## Learning Objectives 

- Learning Objectives

- Identify the external databases accessed for locate requests
- List the types of data available from each locate source
- Identify data that may be available in the future

## External Locate Sources

- Social Security Administration (SSA)
- SSN identification/verification
- Employer name and address
- Address to which retirement/benefits check is being mailed

## External Locate Sources (cont.)

- Department of Defense
- Military duty address
- Pay grade
- Date of separation from service

## External Locate Sources (cont.)

- Internal Revenue Service (IRS)
- SSN
- Address on most recent NCP tax return
- Department of Veterans Affairs (DVA)
- Pension, compensation, and educational
-   benefits
- Amount of benefits
- Address to which check is being sent

## External Locate Sources (cont.)

- Federal Bureau of Investigation (FBI)

- Office of Personnel Management (OPM)
- Federal retirement information

## Future Enhancements

- Some of the additional information to which
- the OCSE would like access:
- Additional Social Security Administration benefits, such as SSI
- Prisoner data maintained by SSA (information from State and Federal prisons)
- Death information maintained by SSA
- 	(54 million records)
- CIA/NSA data

## Module 7: CSENet

- Module 7: CSENet

**Notes:**
18
07/11/98
2

## Learning Objectives 

- Learning Objectives

- Understand when CSENet is used
- Understand how CSENet works
- List CSENet transaction types

**Notes:**
19
07/11/98
8

## What is CSENet? 

- What is CSENet?

**  ****C**hild **S**upport **E**nforcement **Net**work
- Nationwide communications network that
-  		transfers child support case data
- 		between states
- NOT a database
- INTERSTATE case processing tool

**Notes:**
20
07/11/98
9

## Origin of CSENet 

- Origin of CSENet

- Conceived in 1988 to overcome
- 		differences in State CSE systems
- Installed in 1992
- Poised for FPLS in 1998

**Notes:**
21
07/11/98
10

## Purpose of CSENet 

- Purpose of CSENet

- Speedy, accurate, inexpensive information exchange
- Data transfer between state systems
- Standard transactions
- Support follow-up on FCR matches
- Fully automated

**Notes:**
22
07/11/98
11

## What Does CSENet Do? 

- What Does CSENet Do?

- Information gathering
- Quick locate
- Case Information
- Case processing
- Paternity establishment
- Order establishment
- Enforcement
- Collection information

**Notes:**
23
07/11/98
12

## Interstate Communications

**Notes:**
24
07/11/98
13

## CSENet Communications Between States

## Transaction Types

- 1.  Request information
- 2.  Request services
- 3.  Provide information
- All built on State CSE system

**Notes:**
26
07/11/98
14

## Standard Transaction Format 

- Standard Transaction Format

- 1.  Function type code
- 2.  Action code
- 3.  Reason code
- 4.  Data blocks

**Notes:**
27
07/11/98
15

## Case Information (CSI) Transaction 

**Case I**nformation (CSI) Transaction

- October, 1998
- Uses FCR matches
- Completes the FPLS information loop

**Notes:**
28
07/11/98
16

## Transaction Processing 

- Transaction Processing

- 1.		VA drops off transactions to host
- 2. 	Host edits and routes to MD State 2 		mailbox
- 3. 	MD picks up transactions in mailbox
- 4. 	MD takes action on transaction from 	VA

**Notes:**
29
07/11/98
17

## Impact of Welfare Reform on CSENet 

- Impact of Welfare Reform on CSENet

- Expansion of FPLS
- “Missing link”
- Even more automation?

**Notes:**
30
07/11/98
18

## Module 8: Access, Security and Privacy

- Module 8: Access, Security and Privacy

**Notes:**
31
07/11/98
2

## Learning Objectives 

- Learning Objectives

- Understand the “who” and “why” of
- 		access to the FPLS
- Understand what security measures are
- 		in place to protect the data in FPLS

**Notes:**
32
07/11/98
8

## Introduction

- Security is for Staff and Systems
- Security Will Require a Change in How We Do Business
- Security Requires Everyone’s Participation
- Security Benefits Everyone

## Introduction - Good Security Benefits Us

- Protects Staff From Harm and Theft
- Protects Our Programs From Criticism from Auditors, on the Hill and in the Media
- Protects Our Reputation for Safeguarding the Public’s Confidential Information

## Introduction - Good Security Benefits the American People

- Security Protects American Families From Harm Caused by Disclosure of Private Data
- Domestic violence and child abuse
- Financial crimes and fraud
- Security Protects the FPLS and Tax Offset Systems That America’s Families Need
- From hackers & viruses
- From criticism from its opponents

## Physical Security  

- Physical Security

- Restricted Access
- Why?
- To prevent unauthorized individuals from gaining access to sensitive data
- Organization is growing
- Higher visibility
- How?
- “Restricted Access” signs
- Access lists
- Sign-in log book
- Everyone’s cooperation

## Personnel Security

- Why?
- Personnel are the key to the security of the system, they ensure that physical, computer and network security rules are followed.
- Personnel are entrusted with access to highly sensitive personal data about nearly every working American.
- How?
- Training
- Background Investigations
- Non-disclosure Agreements

## Access, Security, Privacy --Sources That Define These Safeguards

- PRWORA
- The Privacy Act of 1974
- The Computer Security Act of 1987
- Internal Revenue Code of 1986
- Office of Management and Budget (OMB)
- 		bulletins and circulars
- Federal Information Processing Standards
- 		(FIPS) Publications

## PRWORA Limits Access to:

- State agencies that administer the Child
- 		Support Program
- Temporary Assistance to Needy
- 		Families
- Foster care and welfare programs
- Secretary of the Treasury
- Commissioner of the Social Security
- 		Administration (SSA)

## PRWORA Limits Access to:

- Researchers pursuing projects
- Authorized persons as defined by Section 453(c) and 463(d) of the Social Security Act
- Courts with authority to issue child support orders

## Family Violence Indicator

- If a State notifies the Secretary of DHHS, via the FCR, that there is evidence of family violence, no information will be disclosed
- State has reason to believe that release of information could result in physical or emotional harm to an individual

## Privacy Act of 1974

- Provides standards for, and restrictions on, records maintained by Federal agencies on individuals
- Establishes who has access to the information and what agencies are authorized to collect the information

## Computer Security Act of 1987

- Improvement of privacy for unclassified, sensitive information in Federal computers
- Preparation and periodic update of  Federal agencies’ computer security plans
- Periodic training in computer security awareness for Federal and contractor employees

## Internal Revenue Code of 1986

- Outlines the provision of civil damages that may be assessed against individuals at the Federal and State levels for unauthorized disclosure of IRS information

## OMB Bulletins and Circulars

- OMB Bulletin No. 90-08
- Provides guidance to Federal agencies about computer security planning activities required by the Computer Security Act of 1987

## OMB Bulletins and Circulars (cont.)

- The OMB Circular No. A-130
- Establishes minimum controls for Federal automated information security programs
- Assigns Federal agency responsibilities for the security of automated information
- Explains what techniques can be used to collect electronic information, and discusses the safeguards that agencies must maintain to protect it

## FIPS Publications

- FIPS Publication 102
- Describes how States should establish and implement a computer security certification and accreditation program
- FIPS Publication 73
- Focuses on controls for use with computer applications and provides guidance to address and prevent inadequacies in their design and operation

## Penalties for Violation of Security Rules

- For the average IV-D worker
- Suspension
- Loss of employment
- Fines
- Jail time
- For States
- Loss of access to secure information