|NASA would like to note that future guidance and configurations must keep pace with industry updates in common operating systems and applications. The FDCC technical guidance and policy releases tend to lag behind software releases. In order to remain relevant and viable, FDCC technical and policy development must advance at the pace of Federal Agency procurements of new commercial software.
Linda Cureton, Chief Information Officer, Agencies Need to Implement Federal Desktop Core Configuration Requirements
Today’s WhatIs.com Word of the Day is Federal Desktop Core Configuration (FDCC).
|“What is different is that we’re going to have comprehensive coverage across federal networks, and that all the information about potential intrusions or malicious code will flow to a central point, the U.S. Computer Emergency Readiness Team at DHS.”
Robert Jamison, as quoted in Analysis: Einstein and U.S. cybersecurity
Today’s WhatIs.com Word of the Day is EINSTEIN.
|In all the fervent testimonials to the benefits of automated and optimized medical practice, the panel seemed to be glossing over a roadblock familiar to CIOs of any industry: users who might not cotton to an automated system.|
Today’s WhatIs.com Word of the Day is Amalga
Today’s WhatIs.com Word of the Day is MultiSpeak.
WIN Energy chose MultiSpeak as the vehicle to enable a Best of Breed strategy and optimize the way the cooperative does business. WIN Energy can now select the various software technologies that are the best fit for the utility and, as long as the software packages are MultiSpeak compliant, they will function together regardless of software version upgrades. WIN Energy’s first MultiSpeak implementation between its accounting system, NISC’s CAPSXL+, and its automated field staking package, MiniMax’s StakeOut, was both highly successful and its first step towards a truly system-wide approach.
I really liked the PowerPoint on Transparency and Open Government put together by SanFrancisco’s CIO Chris Vein and CTO Blair Adams. The show is interesting visually and they do a great job documenting how the city/county of SanFrancisco is addressing challenges.
Here are their 8 Principles for Gov 2.0
– All public data are made available. Public data are not data
that are subject to valid privacy, security or privilege
– Data are collected at the source, with the finest possible
level of granularity, not in aggregate or modified forms.
– Data are made available as quickly as necessary to preserve
the value of the data
– Data are available to the widest range of users for the
widest range of purposes.
• Machine Processable
– Data are reasonably structured to allow automated processing.
–Data are available for anyone, with no requirement of
–Data are available in a format over which no entity has exclusive
–Data are not subject to any copyright, patent, trademark, or
trade secret regulation. Reasonable privacy, security and privilege
restrictions may be allowed.
Am looking at conferences to see if I can pick out trends.
e.Republic posts speaker slides from their conferences after the event is over. I think the slides provide an interesting peak behind the curtain.
GTC Southwest: The Texas Digital Government Summit 2010
California CIO Academy 2010
|You can’t telework with paper. We need to get to where we can work on documents on a screen. Did you ever see anyone on ‘Star Trek’ carrying a clipboard? We need to get to a point where there’s no need for a desk except as a place to put your lunch.
Wayne Leiss as quoted in The future of telework technology: A wish list
Wayne Leiss is chief information officer at the Treasury Department’s Office of Thrift Supervision.
Other items on the wish lists of telework managers include:
- The ability to share documents and edit jointly, and large screens to keep the documents readable.
- Better virtual private networks and more use of them.
- A wider array of options for devices, including a range of laptop computer screen sizes.
- Access to applications based on individual needs rather than enterprise-wide delivery.
Security is key. You need two-factor encryption, you need hard drive encryption
|The previous approach was to protect everything and share what you must. Now the focus is to share everything and protect what you must. But culturally a lot of people were still very uncomfortable with releasing all that data.
Sonny Bhagowalia, as quoted in Sonny Bhagowalia smashes technical, cultural obstacles to sharing government data
Sonny Bhagowalia is the chief information officer at the Interior Department.
We have 24,000 domains in the U.S. government and millions of Web pages. So the idea was to start connecting them and making it easier to find data from all those sites.
Everything we do in our lives is about information and data. I like to say that it’s not about the technology, it’s about the data. And when data is found in context, it becomes information. That whole continuum of data and then information is really where the world is going.
|GSA directs more than 80 percent of its IT spending to the operation and maintenance of existing systems, leaving only the remainder to invest in new technologies.
Casey Coleman,as quoted in The CIO 14 years later: Power vs. paperwork
|The most obvious impacts will be seen in how this [document] brings the national security community closer to legislative compliance requirements, assists our inspector general audits, and aligns with the rest of the federal government to support reciprocity…the document provides an approach to manage risks for both traditional and complex systems, a procedure that was not formalized previously.
Roger L. Caslow,as quoted in New Document Provides Framework for Interagency Data Sharing
Roger L. Caslow is chief of the Risk and Information Assurance Program Division, Office of the Associate Director of National Intelligence and Chief Information Officer. He’s talking about NIST Special Publication 800-37, Revision 1, Guide for Applying the Risk Management Framework to Federal Information Systems: A Security Life Cycle Approach (NIST SP 800-37) and apparently he doesn’t like to have his picture taken.
Henry Kenyon describes the special publication as a six-step risk management framework (RMF); a common information security framework for the federal government and the contractors who support it. The official diagram is below: