ARC Outreach on HSPD 12 and Mandatory Use of ODIN



Similar documents
GOALS (2) The goal of this training module is to increase your awareness of HSPD-12 and the corresponding technical standard FIPS 201.

NOAA HSPD-12 PIV-II Implementation October 23, Who is responsible for implementation of HSPD-12 PIV-II?

NSF AuthentX Identity Management System (IDMS) Privacy Impact Assessment. Version: 1.1 Date: 12/04/2006. National Science Foundation

DEPARTMENTAL REGULATION

Audio: This overview module contains an introduction, five lessons, and a conclusion.

Smart Cards and Biometrics in Physical Access Control Systems

2. Each server or domain controller requires its own server certificate, DoD Root Certificates and enterprise validator installed.

How to Use Your LincPass Credential

The Convergence of IT Security and Physical Access Control

GAO PERSONAL ID VERIFICATION. Agencies Should Set a Higher Priority on Using the Capabilities of Standardized Identification Cards

The Government-wide Implementation of Biometrics for HSPD-12

This document is uncontrolled when printed. Before use, check the Master List to verify that this is the current version. Compliance is mandatory.

Justice Management Division

Identity, Credential, and Access Management. An information exchange For Information Security and Privacy Advisory Board

Desktop Transition Team Report

U.S. DEPARTMENT OF COMMERCE UNITED STATES PATENT AND TRADEMARK OFFICE. Privacy Impact Assessment

How To Get A Piv Credential

The Benefits Buzz. New Financial Planning Tool

Status: Final. Form Date: 30-SEP-13. Question 1: OPDIV Question 1 Answer: OS

DEPARTMENTAL DIRECTIVE

Announcing Approval of Federal Information Processing Standard (FIPS) Publication 201-2,

Derived credentials. NIST SP ( 5.3.5) provides for long term derived credentials

NIST s FIPS 201: Personal Identity Verification (PIV) of Federal Employees and Contractors Masaryk University in Brno Faculty of Informatics

1. The human guard at the access control entry point determines whether the PIV Card appears to be genuine and has not been altered in any way.

HSPD-12 Homeland Security Presidential Directive #12 Overview

NASA PIV smartcards at Headquarters Frequently Asked Questions (FAQ s)

U.S. Department of Housing and Urban Development

Identity - Privacy - Security

Moving to Multi-factor Authentication. Kevin Unthank

2012 FISMA Executive Summary Report

Deriving a Trusted Mobile Identity from an Existing Credential

What Does it Mean to be PIVish in PACS ICAM PIV in E-PACS Guidance v2.0.2 the short form. December 3, 2012

GOVERNMENT USE OF MOBILE TECHNOLOGY

IDaaS: Managed Credentials for Local & State Emergency Responders

The Convergence of IT Security and Physical Access Control

Federal Identity Management Handbook

Understanding the differences in PIV, PIV-I, PIV-C August 23, 2010

Interagency Advisory Board Meeting Agenda, March 5, 2009

Evaluation Report. Weaknesses Identified During the FY 2013 Federal Information Security Management Act Review. April 30, 2014 Report Number 14-12

Small Business Administration Privacy Impact Assessment

CMS Operational Policy for VPN Access to 3-Zone Admin and Development /Validation Segments

I N F O R M A T I O N S E C U R I T Y

HSPD-12 Implementation Architecture Working Group Concept Overview. Version 1.0 March 17, 2006

FOUR PILLARS FOR A SUCCESSFUL PIV ECOSYSTEM

NASA DESK GUIDE FOR SUITABILITY AND SECURITY CLEARANCE PROCESSING. Version 2

Identity and Access Management Initiatives in the United States Government

Identity, Credential, and Access Management. Open Solutions for Open Government

FEDERAL IDENTITY, CREDENTIAL, AND ACCESS MANAGEMENT AND PERSONAL IDENTITY VERIFICATION (PIV) SOLUTIONS

Information Technology Policy

Appendix 10 IT Security Implementation Guide. For. Information Management and Communication Support (IMCS)

I N F O R M A T I O N S E C U R I T Y

CoSign by ARX for PIV Cards

U.S. Department of Energy Washington, D.C.

Privacy Impact Assessment of. Personal Identity Verification Program

US Security Directive FIPS 201

esign Online Digital Signature Service

GSA FIPS 201 Evaluation Program

Personal Identity Verification (PIV) of Federal Employees and Contractors

Implementing Federal Personal Identity Verification for VMware View. By Bryan Salek, Federal Desktop Systems Engineer, VMware

Enrolling with PIV and PIV-I Velocity Enrollment Manager

NATIONAL CREDIT UNION ADMINISTRATION OFFICE OF INSPECTOR GENERAL

Security Language for IT Acquisition Efforts CIO-IT Security-09-48

Mission Assurance and Security Services

MEMORANDUM FOR THE HEADS OF DEPARTMENTS AND AGENCIES

How To Navigate The Maze In Your Organization

NEIS HELP DESK FAQS. HSPD-12 Policy/Business Process. General HSPD-12 FAQs can be found online at:

Department of Veterans Affairs VA DIRECTIVE 6510 VA IDENTITY AND ACCESS MANAGEMENT

Report No. D June 23, DoD Implementation of Homeland Security Presidential Directive-12

PRIVACY IMPACT ASSESSMENT

Card Management System Integration Made Easy: Tools for Enrollment and Management of Certificates. September 2006

Practical Challenges in Adopting PIV/PIV-I

~ Final Credentialing Standards for Issuing Personal Identity Verification Cards under HSPD-12

Department of Defense INSTRUCTION

5 FAM 620 INFORMATION TECHNOLOGY (IT) PROJECT MANAGEMENT

Department of Defense SHA-256 Migration Overview

PIV Data Model Test Guidelines

Report via OMB s Integrated Data Collection (IDC), 10

Expiring Certificates on LincPass Cards

STATEMENT OF WORK. For

DEPARTMENT OF DEFENSE GUIDEBOOK FOR CAC-ELIGIBLE CONTRACTORS FOR UNCLASSIFIED NETWORK ACCESS

E X E C U T I V E O F F I CE O F T H E P R E S I D EN T

Executive Summary P 1. ActivIdentity

Information Security Program Management Standard

Federal Identity, Credential, and Access Management (FICAM) Roadmap and Implementation Guidance

Federal Communications Commission Office of the Managing Director

The Social Security Administration s Internal Controls over Issuing and Monitoring Contractors Homeland Security Presidential Directive-12 Credentials

Name of Policy: Wireless communication business expenses paid through any University of Toledo funds. Policy Number:

SecurityManager. Enterprise Personnel & Physical Security Case Management Solution for Federal Agencies

Department of Veterans Affairs VA Directive 0710 PERSONNEL SECURITY AND SUITABILITY PROGRAM

Vulnerability Management Policy

Using FIPS 201 and the PIV Card for the Corporate Enterprise

U.S. DEPARTMENT OF COMMERCE UNITED STATES PATENT AND TRADEMARK OFFICE. Privacy Impact Assessment

Personal Identity Verification (PIV) of Federal Employees and Contractors DRAFT

Dublin City University

For Official Use Only (FOUO)

FITSP-Auditor Candidate Exam Guide

Personal Identity Verification (PIV) of Federal Employees and Contractors

IT Compliance in Acquisition Checklist v3.5 Page 1 of 7

TREASURY INSPECTOR GENERAL FOR TAX ADMINISTRATION

Transcription:

ARC Outreach on HSPD 12 and Mandatory Use of ODIN August 28 & 29, 2007

Agenda Center Management Opening Remarks CIO Perspective Homeland Security Presidential Directive (HSPD) 12 Questions & Answers Mandatory Use of ODIN Mission Focus Review (MFR) Decisions Questions & Answers 2

Strategic Overview-Why NASA spends a lot of money on IT ($2.2 Billion). We need to be more efficient with our IT investments. Proliferation of tools and lack of standards to enable integration Its difficult to work seamlessly across Center boundaries Lack of credibility in IT Security 3

Benefits Efficiency eliminate unnecessary duplication, reduction of IT Security Certification and Accreditation (C&A) costs Economies of Scale Visibility into Total Cost of Ownership (TCO) Improved Security Interoperability Ability to work seamlessly across NASA Alignment with Directives 4

Homeland Security Presidential Directive (HSPD) -12

Background President signs Homeland Security Presidential Directive (HSPD-12) in August 2004 Government-wide standard for Identification NIST assigned to develop the standard OMB assigned to implement the standard OMB issues implementation guidance August 2005 Current Standard for ID (FIPS 201) issued March 2006 OMB implementation guidance: Rebadge by October 2007 Use PIV badge with all computer systems by October 2010 Emphasis right now is on rebadging Approximately 4000 people at Ames After rebadging (2008-2010) emphasis will shift to expanded use of the new badge Can t use the badge unless you have one Focus through 2010 will be on using badge for computer system access We know there are a lot of questions about HSPD-12 In on-going dialog with the Ames Union and the Ames Contractor Council After we go over the material, we will open it up for 15-20 minutes to you can ask questions SME s here (HR, legal, Acquisitions, Facility Access, PSO., Legal, Tech. Devl. team) The scope is broad and all the implementation decision have not been made -- we ll do our best to answer 6

Homeland Security Presidential Directive 12 (HSPD-12) HSPD-12 mandates a government-wide standard for secure and reliable forms of identification for Agency and contractor employees used for access to Federal facilities and information systems. What it Means to Us: New badges will be issued that will have the following advantages: Minimizes the number of passwords to remember (Note: This is a future capability within approximately two years) which requires other information systems infrastructure to be implemented); Reduces the risk of identity theft by increasing protection of personal privacy; and Interoperability across the Agency for access to facilities and information systems. 7

What s on the Badge Printed on Front: 1. Name 2. Badge number 3. Affiliation 4. Expiration date 5. Center Printed on back: 1. Height 2. Hair color 3. Eye color Civil Servant Configuration Embedded Computer Chip Containing: 1. Badge holder Card Holder Unique Identification (CHUID) number 2. User PIN 3. PKI certificate 4. Biometric identification (fingerprint minutia) 8

HSPD-12: Key Dates 2007 July Begin enrollment for new badges August Begin quantity issuance of new badges September Use badge for access to all applications and systems (physical access) categorized as High, per FIPS 199 October Complete background investigation process for civil service and contractor employees 2008 2010 April Begin to equip all desktop computers with card readers and middleware September Use badge to access all moderate applications September Use badge for all applications/ systems 9

Steps to Getting a New Badge Step 1: Background Investigation (BI) Civil Servants have BI when hired Old BI being used for badge issuance purposes New requirement for period reinvestigation Civil Servants with BIs older than 10 years to be reinvestigated starting soon Contractors undergoing BI process now All contractors have, at this point, been invited by Personnel Security office to submit information to OPM e-qip Once e-qip filled out, meeting with Personnel Security Specialist at Bldg 566 to obtain signed forms and complete final review before submission to OPM Fingerprints must also be submitted as part of BI process 10

Steps to Getting a New Badge (continued) Step 2: Personal Identity Verification (PIV) Enrollment Everyone who will receive a NASA PIV-2 badge must go through enrollment Practice and training taking place now Code JP and JT serving as guinea pigs You will receive an e-mail asking you to schedule an appointment via a web-based scheduling tool You will have a limited time window to complete your appointment, which will be at Bldg 566 The e-mail will also tell you what forms of identification must be brought with you to the appointment Two forms of I-9 identity documents are required PIV Enrollment includes: Digital photo Digital fingerprints Digital signature Scanning of two forms of I-9 identity documents Expect 30 minutes Hoping that practice will speed this up 11

Steps to Getting a New Badge (continued) Step 3: Badge Issuance Everyone who will receive a NASA PIV-2 badge must go through badge issuance Agency still in testing of final badge to ensure it meets specifications You will receive another e-mail asking you to schedule an appointment via a web-based scheduling tool You will have a limited time window to complete your appointment, which will also be at Bldg 566 Badge issuance includes: Encoding of badge Single finger flat fingerprint check Selection of a Personal Identification Number (PIN) Do not yet know how long this process will take Should be much quicker than PIV enrollment 12

Locksmith Shop Bldg 566 McDonalds 13

Very Important The Center has a limited time window for re-badging due to the near-term OMB deadline and high resource requirements for the effort There will not be time to make two passes at enrollment and badge issuance Once notified to do so: Make your appointment Keep your appointment.unless you have a legitimate reason Your cooperation and promptness will be appreciated! 14

Important Web Sites & Contact Information For more information, visit: http://hspd12.arc.nasa.gov/ http://cio.arc.nasa.gov/index.htm If you have any questions, email: archspd12@mail.arc.nasa.gov 15

Questions & Answers 16

Relax... Take a deep breath

Outsourcing Desktop Initiative for NASA (ODIN) Mission Focus Review (MFR) Decisions 18

Mandatory Use of ODIN The agency Strategic Management Council (SMC) has approved two Mission Focus Reviews (MFR)s related to ODIN The SMC decision includes: MFR#7 - Consolidate all cellular services (pagers, cell phones, smartphones/pdas, and cellular Internet) under ODIN MFR#137 - Consolidate all laptop/desktop/workstation procurement and support under ODIN Why? Improved visibility and management of IT resources Improved configuration management and IT security Alignment with federal directives (OMB, Executive Orders) Improved cost performance for procuring and supporting IT resources 19

Benchmarking GRC migrated to ODIN in 2000 ODIN Support includes desktops and workstations, cell phones, and other Communications services About 95% of GRC is currently supported by ODIN Cost for ODIN has generally decreased Except for a two years when large network infrastructure upgrades occurred FY05-FY07 - overall cost decrease and per seat cost decrease Cost savings are achieved without incorporating inflation 20

Scope & Status of MFR#7 Scope of MFR#7 Pagers Cell phones All Smartphones/communicating PDAs such as Blackberrys, Treos, iphones, Windows Mobile devices, etc. The Agency does not currently approve the purchase or support of iphones Agency Guidance document is pending All cell phone services (voice, data, etc.) Status of MFR#7 ~90% of the center already is using ODIN for these services Identify & Migrate non-odin users Centerwide message ARC ODIN will be adding new cell phone providers 21

Scope of MFR#137 All desktops, laptops and workstations Includes both General Purpose and Scientific & Engineering systems (Windows, Mac, and Unix/Linux) Exception only by written, approved, and reported waiver All civil servants and on/near-site contractors that require access to the NASA network Does not include: Embedded processors (e.g. flight and ground support equipment) Lab equipment (e.g. laser equipment, oscilloscopes) Servers: web, database, clusters (dedicated servers) Deep Space Network 22

Status of MFR#137 Mainly administrative systems (about 1/3 of users) Augmenting ODIN capabilities Getting the word out Briefed CIO Council Meetings with Union Meetings with Procurement Started organization specific discussions Assessing center s readiness for transition - ODIN ORR Reviewing Ames business model approach to ODIN Very high-level DRAFT Transition Plan submitted to HQ on 8/22 Met with Lockheed Martin IT Vice President on 8/23 Planning outreach and training program 23

Key ODIN Dates MFR#7 (pagers, cell phones, Smartphones/PDAs, and cellular services) Effective Immediately - Purchase cards may no longer be used to procure the MFR#7 items except through ODIN I-Phones Guidance: Until I-Phones are supported and covered by a security plan, they are prohibited for purchase for Government business. (Agency Guidance document is pending) Not later than September 30, 2007 Identify remaining 10% of people needing to migrate MFR#7 items to ODIN Contracts will no longer be used to procure the MFR#7 items except through ODIN Not later than January 31, 2008 Migrate remaining 10% MFR#7 non-odin users MFR#137 (desktops, laptops, workstations & support for these systems) Effective Immediately Orders for administrative desktop systems going through Serv-I will be screened and re-directed to ODIN Orders for LINUX/UNIX systems are business as usual until further notice Not later than October 31, 2007 - Identify non-odin users and schedule ODIN ORR NLT February 2009: Target completion for ODIN transition 24

ODIN Transition Team Established ODIN Transition Planning & Implementation Team Membership: ODIN DO-COTR/COTR*, Susan Parkhurst Alternate ODIN DO-COTR/COTR - TBD CO, Veronica Llamas Ed Sheffner Annett Randall Jason Duley Matt Linton Kevin Jones * Delivery Order - Contracting Officer Technical Representative (DO-COTR) 25

ODIN Transition Strategy Identify contract issues/dates Collaborate with other Centers Education & Outreach Program BOFs, Training of ODIN POCs, & End-user training Floater Dedicated System Administrator (DSA) Continue to identify Center customer concerns/issues Work with organization ODIN POCs & Lockheed Martin to ensure they are ready to respond to the increased usage of ODIN Develop a phased schedule approach 26

References & Contact Information For more information, visit http://www.odin.lmit.com/arc http://cio.arc.nasa.gov/index.htm If you have any questions, email: odinprojectoffice@mail.arc.nasa.gov 27

Take-Away s HSPD-12, NOMAD, and ODIN are top priorities What you can do: Review X.500 information and make any necessary corrections at https://arcapps.arc.nasa.gov/ 28

Questions & Answers 29