recommended reading

Rep. Connolly introduces CTO legislation to codify executive branch job

Legislation that would statutorily codify the White House chief technology officer position was introduced Thursday by Rep. Gerald Connolly, D-Va., who believes the job, proposed by President Obama on the campaign trail, is too important to isolate in a single administration. Making the CTO a permanent position in the executive branch will give the individual "greater stature and empower him/her to accomplish the goals of the president," he wrote in a "Dear Colleague" letter circulated the same day. Obama has not yet selected his CTO but did tap former District of Columbia e-government expert Vivek Kundra to become the federal government's CIO.

Obama has said the CTO will ensure that the government and all its agencies have the right infrastructure, policies and services for the 21st century. The individual will also ensure the safety of high-tech networks and will lead an interagency effort, working with CTOs and CIOs in each of the federal agencies, to ensure that they use best-in-class technologies and share best practices, according to Connolly's letter. The bill would provide the official with resources that are necessary to complete his or her mission, including the ability to convene hearings, conduct studies, establish advisory panels, and award grants and fellowships.

Earlier this year, Connolly and Rep. Jim Moran, D-Va., wrote to Obama praising him for signing the executive order that created the CTO post and recommended Virginia CTO Aneesh Chopra for the job. They said Chopra's public and private experience in the technology field made him the right candidate. They also noted his focus on healthcare IT "is ideal for a position that will have responsibilities dealing both with stimulus spending on healthcare and environmental programs." Moran and Del. Madeleine Bordallo, D-Guam, have signed on as cosponsors of the CTO Act.

Threatwatch Alert

Thousands of cyber attacks occur each day

See the latest threats


Close [ x ] More from Nextgov

Thank you for subscribing to newsletters from
We think these reports might interest you:

  • Featured Content from RSA Conference: Dissed by NIST

    Learn more about the latest draft of the U.S. National Institute of Standards and Technology guidance document on authentication and lifecycle management.

  • PIV- I And Multifactor Authentication: The Best Defense for Federal Government Contractors

    This white paper explores NIST SP 800-171 and why compliance is critical to federal government contractors, especially those that work with the Department of Defense, as well as how leveraging PIV-I credentialing with multifactor authentication can be used as a defense against cyberattacks

  • Toward A More Innovative Government

    This research study aims to understand how state and local leaders regard their agency’s innovation efforts and what they are doing to overcome the challenges they face in successfully implementing these efforts.

  • From Volume to Value: UK’s NHS Digital Provides U.S. Healthcare Agencies A Roadmap For Value-Based Payment Models

    The U.S. healthcare industry is rapidly moving away from traditional fee-for-service models and towards value-based purchasing that reimburses physicians for quality of care in place of frequency of care.

  • GBC Flash Poll: Is Your Agency Safe?

    Federal leaders weigh in on the state of information security

  • Data-Centric Security vs. Database-Level Security

    Database-level encryption had its origins in the 1990s and early 2000s in response to very basic risks which largely revolved around the theft of servers, backup tapes and other physical-layer assets. As noted in Verizon’s 2014, Data Breach Investigations Report (DBIR)1, threats today are far more advanced and dangerous.


When you download a report, your information may be shared with the underwriters of that document.