National Strategy for Trusted Identities in Cyberspace

The National Strategy for Trusted Identities in Cyberspace (NSTIC) is a US government initiative announced in April 2011 to improve the privacy, security and convenience of sensitive online transactions through collaborative efforts with the private sector, advocacy groups, government agencies, and other organizations.[1]

The strategy imagined an online environment where individuals and organizations can trust each other because they identify and authenticate their digital identities and the digital identities of organizations and devices.[2] It was promoted to offer, but not mandate, stronger identification and authentication while protecting privacy by limiting the amount of information that individuals must disclose.[3]

Description

The strategy was developed with input from private sector lobbyists, including organizations representing 18 business groups, 70 nonprofit and federal advisory groups, and comments and dialogue from the public.

The strategy had four guiding principles:[4]

  1. privacy-enhancing and voluntary
  2. secure and resilient
  3. interoperable
  4. cost-effective and easy to use.

The NSTIC described a vision compared to an ecosystem where individuals, businesses, and other organizations enjoy greater trust and security as they conduct sensitive transactions online. Technologies, policies, and agreed upon standards would securely support transactions ranging from anonymous to fully authenticated and from low to high value in such an imagined world. Implementation included three initiatives:

NSTIC was announced during the Presidency of Barack Obama near the end of his first term on April 15, 2011.[1] A magazine article said individuals might validate their identities securely for sensitive transactions (such as banking or viewing health records) and let them stay anonymous when they are not (such as blogging or surfing the Web).[8]

In January 2011 the U.S. Department of Commerce had established a National Program Office (NPO), led by the National Institute of Standards and Technology, to help implement NSTIC.[9] To coordinate implementation activities of federal agencies, the NPO works with the White House Cybersecurity Coordinator, originally Howard Schmidt[3] and then after 2012 Michael Daniel.[10]

Steering Group

The NSTIC called a steering group led by the private sector to administer the development and adoption of its framework. This Identity Ecosystem Steering Group (IDESG) held a meeting in Chicago August 15–16, 2012.[11] The meeting brought together 195 members in person and 315 members remotely. Additional plenary meetings were in Phoenix, Arizona,[12] Santa Clara, California[13] and Boston, Massachusetts. Under a grant from 2012 through 2014, Trusted Federal Systems, Inc. was the group’s administrative body.[14]

Pilots

The federal government initiated and supported pilot programs. In 2012, NSTIC awarded $9 million to pilot projects. For example, the American Association of Motor Vehicle Administrators was developing a demonstration of commercial identity provider credentials by the Virginia state government, including securely verifying identities online with the Virginia Department of Motor Vehicles.[15] The Internet2 received about $1.8 million for research.[15]

Federal Cloud Credential Exchange (Connect.Gov)

The NSTIC called for U.S. federal government agencies to be early adopters of the Identity Ecosystem envisioned in NSTIC.[16] Agencies struggled to implement it for services they provide internally and externally. Technical, policy and cost barriers made it challenging to accept third-party credential providers accredited by the Federal Identity, Credential, and Access Management (FICAM) initiative.[17]

In response, the White House created a Federal Cloud Credential Exchange (FCCX) team, co-chaired by NSTIC and the General Services Administration. The team consisted of representatives from agencies whose applications are accessed by a large population of external customers. In November 2012, the United States Postal Service was chosen to manage a pilot version of the FCCX, and awarded the contract to build it to SecureKey Technologies, a member of FIDO Alliance. That contract was renewed in May, 2015.[18][19]

Connect.Gov was launched in December, 2014, the manifestation of this pilot. The first two companies to provide individual US citizens Identity Management services compatible with Connect.Gov, were ID.me and Verizon.[20] Ping Identity and Forgerock were the first software platforms to provide FICAM-compliant credentials, and enable private sector organizations to connect securely to government agencies, a primary objective of this project.[21][22]

Criticism

The proposal generated criticism since it was released in draft form in June 2010.[3][23] Much centered around privacy implications of the proposal.

Shortly after the draft's release, the Electronic Privacy Information Center (EPIC), with other consumer-rights and civil liberties organizations, sent the committee a statement in response to the draft NSTIC policy, requesting a clearer and more complete plan to create and safeguard Internet users' rights and privacy.[24] While EPIC head, Marc Rotenberg, called NSTIC "historic," he also cautioned that "...online identity is complex problem and the risk of 'cyber-identity theft' with consolidated identity systems is very real. The US will need to do more to protect online privacy."[25]

NSTIC addressed some early privacy concerns through its 2013 fair information practice principles document.[26] Subsequent initiatives sought to advance privacy. For example, the American Civil Liberties Union and the Electronic Frontier Foundation were involved in a privacy committee in the IDESG.

References

  1. 1 2 "Administration Releases Strategy to Protect Online Consumers and Support Innovation and Fact Sheet on National Strategy for Trusted Identities in Cyberspace". Press release (Office of the White House). April 15, 2011. Retrieved November 9, 2013.
  2. ↑ "National Strategy for Trusted Identities in Cyberspace" (PDF). April 14, 2011. Retrieved November 9, 2013.
  3. 1 2 3 Howard A. Schmidt (June 25, 2010). "The National Strategy for Trusted Identities in Cyberspace". The White House Blog. Retrieved November 9, 2013.
  4. ↑
  5. ↑
  6. ↑
  7. ↑
  8. ↑ Mat Honan (November 15, 2012). "Kill the Password - Why a String of Characters Can't Protect Us Anymore". Wired Gadget Lab. Retrieved November 9, 2013.
  9. ↑ "National Program Office Planned for Online Trusted Identity Strategy". Press release (NIST). January 19, 2011. Retrieved November 10, 2013.
  10. ↑ "Michael Daniel: Special Assistant to the President and Cybersecurity Coordinator". White House Profile. Retrieved November 9, 2013.
  11. ↑
  12. ↑
  13. ↑
  14. ↑ "NSTIC Welcomes Trusted Federal Systems as Secretariat of the Identity Ecosystem Steering Group". NSTIC blog. July 12, 2012. Retrieved November 9, 2013.
  15. 1 2 "Five Pilot Projects Receive Grants to Promote Online Security and Privacy". Press release (NIST). September 20, 2012. Retrieved November 10, 2013.
  16. ↑
  17. ↑
  18. ↑
  19. ↑
  20. ↑
  21. ↑ Fontana, John (April 30, 2015). "Connect.Gov solidifies, expands ID credential plan for federal agencies". ZD Net. Retrieved May 6, 2015.
  22. ↑ Miller, Jason (December 22, 2014). "Connect.gov is latest attempt to get buy-in to online ID management". Federal News Radio. Retrieved May 6, 2015.
  23. ↑ Lance Whitney (June 28, 2010). "White House drafting plan for cyberspace safety". CNet news. Retrieved November 9, 2013.
  24. ↑ Lillie Coney; et al. (September 23, 2010). "Statement on the National Strategy for Trusted Identities in Cybersecurity Creating Options for Enhanced Online Security and Privacy" (PDF). Privacy International and Electronic Privacy Information Center. Retrieved November 9, 2013.
  25. ↑
  26. ↑ "Appendix A – Fair Information Practice Principles" (PDF). NSTIC. April 4, 2013.

External links

This article is issued from Wikipedia - version of the Tuesday, September 01, 2015. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.