IT Compliance Advisor


January 25, 2010  5:06 PM

Melissa Hathaway on managing cybersecurity, FISMA compliance reforms

GuyPardon Guy Pardon Profile: GuyPardon

In this podcast, former cybersecurity director Melissa Hathaway talks about emerging cybersecurity threats, reforms to FISMA compliance and corporate cyberespionage. Hathaway is a senior adviser at Harvard Kennedy School of Government’s Belfer Center for Science and International Affairs.

Melissa HathawayWhen you listen to the podcast, moderated by SearchCompliance.com associate editor Alexander B. Howard, you’ll hear Hathaway’s answers to the following questions and more:

  1. How could the potential FISMA compliance reforms — so-called “FISMA 2″ — affect the quality of cybersecurity readiness in U.S. government agencies and contractors? Does FISMA compliance need reform?
  2. Other elements of legislation would introduce certification for IT security professionals. Is that a positive outcome, if it happens? Why or why not?
  3. The U.S. House passed a national data breach notification bill before the holiday break. If it passes the Senate, there will be a national standard. What do you think of the prospect? Is such a breach notification bill needed to supplement HHS and FTC data breach regulations?
  4. One critical area in cybersecurity lies in the many data breaches of corporate intellectual property. How does that unfortunate trend relate to compliance? Will a federal data breach notification law help to at least expose the scope of the issue?
  5. There’s considerable concern in the defense community about electronic espionage. How can those entrusted with maintaining cybersecurity balance privacy issues, civil rights and the need to protect or defend critical infrastructure? What does privacy mean in the context of cyberwar?

January 22, 2010  5:29 PM

Network mapping and leak detection at DISA

GuyPardon Guy Pardon Profile: GuyPardon

The Defense Information Systems Agency (DISA) has entered into a multiyear enterprise contract to use Lumeta Inc.’s IPsonar for network mapping and leak detection for the Department of Defense (DoD) global networks.

TKC Global, a systems integrator, will deploy the system.

I interviewed Mark Orndorff, director of DISA’s Program Executive Office for Information Assurance and NetOps, after the announcement last week.Mark Orndorff, DISA

Why is IPsonar considered necessary?
The short answer is, you can’t defend what you don’t know. We consider leak detection and mapping as key requirements to fully understand DoD’s networks and our external connections. This capability directly supports one of the actions in DISA’s recently signed Campaign Plan, where we want to conduct cross-domain searches for leaks between networks. IPsonar will provide a good start towards that requirement.

What networks will it be used on?
IPsonar will be used on SIPRNet [Secret Internet Protocol Router Network] and NIPRNet [Nonsecure Internet Protocol Router Network].

How well has it worked on the SIPRNet?
The “good” news is that we’ve had limited success with this tool on SIPRNet. I view it as good news because the problems we have getting a network mapping tool to work are directly tied to the security controls we’ve implemented to limit the ability of an adversary to maneuver on our networks. The vendor has made some changes to make it easier to work through some of these issues, plus we are now working a revised CONOPS [Concept of Operations] that will put the tool in the hands of those best able to make the network changes needed for the tool to be fully effective.

Is the software used for one-time or periodic network mapping? Or does it run continuously?
I would like to see this run continuously, at least the portion of the tool that supports leak detection. We are working now with JTF GNO [Joint Task Force-Global Network Operations] and the services to finalize the CONOPS.

Once the network or networks are mapped, then what does DISA do?
DISA’s role here is as the acquisition and support agency for an enterprise information assurance capability that will be operated by the COCOMS [DoD's combatant commands], services and agencies. We are responsible for lifecycle support of the capability.

Is DISA planning other steps to increase network security?

Absolutely. We have a large information assurance program that includes a number of initiatives to reduce the attack surface, improve information sharing and provide the global situational awareness needed to assure mission success in the face of cyberattack.

How will IPsonar relate to the transition from IPv4 to IPv6?
We will always have a requirement to understand our network topology and identify leaks. Today, IPsonar can detect, query and capture info from IPv6 assets. The IPsonar solution is sitting on an IPv4 stack but they have identified in their roadmap and are on track to be IPv6-compliant. We will work with the vendor and IPv6 test efforts in DoD to make sure this and all of our IA [Internal Audit] capabilities remain effective as we transition to IPv6.

How will this deployment relate to complying with the Trusted Internet Connections Initiative?

We have strong policy and procedures to support the Trusted Internet Connection Initiative. The leak-detection capability of IPsonar provides the technology to help identify any unapproved Internet connections.

How will this implementation allow DISA and the DoD to meet FISMA compliance standards?

This will support the FISMA requirement for “asset awareness” by providing a mapping capability.

Why choose IPsonar, vs. other networking mapping software?

Our most critical requirement was leak detection. When we considered that, along with the mapping requirements, we found IPsonar to be the best solution.

How will IPsonar integrate with existing network, storage and endpoint security software at DISA to ensure better cybersecurity?
We have a number of cybersecurity solutions providing valuable data for our network defenders, but integration is largely manual. One of the top priorities for us in FY10 is to address this issue. We have two efforts ongoing: one focused on configuration management and vulnerability management requirements leveraging the SCAP data standards, with the other focused on attack detection, diagnosis and response. Both of these efforts will integrate IPsonar to help put data from other sources into context.


January 5, 2010  6:47 PM

IT security and health care compliance resources to start 2010 strong

GuyPardon Guy Pardon Profile: GuyPardon

Last week, we looked back at the top IT compliance management news stories of 2009. From tougher state data protection laws to compliance in the cloud, 2009 held plenty of IT compliance management headaches. We’ll be posting our predictions for 2010 later this week. In the meantime, IT professionals have arrived back in the office and are confronted with the same compliance challenges that existed before the holidays.

What to do?

First, focus on compliance.

1. Build data protection around intrusion detection and access controls.

As contributor John Weathington recommends, begin with a comprehensive data governance and compliance strategy and build data protection practices upon intrusion detection and access controls.

2. Look to the Unified Compliance Framework for common ground.

Compliance professionals and vendors are turning to the Unified Compliance Framework as a common language for overlapping compliance standards.

3. Review our FAQ on mandatory encryption standards and IT operations.

Learn how emerging mandatory encryption standards will affect IT operations.

4. Get a grip on addressing compliance requirements in cloud computing contracts.

As CIOs look to cloud computing for data backup and storage, compliance requirements must be spelled out and met, or the data will be brought back down to earth.

Second, focus on IT security.

The following compliance resources from SearchSecurity.com will be helpful to IT professionals preparing for renewed security challenges this year.

1. Learn how to create an identity theft prevention plan for FTC Red Flags Rules.

Under the FTC’s Red Flags Rules, all financial institutions and creditors with covered accounts are required to create an identity theft prevention plan. The FTC may have extended the enforcement deadline for the Red Flags Rule to June 1, 2010, but five months will go by quickly.

2. Review this guide to internal and external network security auditing.

Contributor Stephen Cobb covers the baseline network audit processes that a security professional should absolutely conduct regularly.

3. Consider the benefits of ISO 27001 and ISO 27002 certification for your enterprise.

If your enterprise is considering becoming ISO 27001 and 27002 certified, there are several important questions to ask.

4. Get up to speed on privileged account management.

Sarbanes-Oxley compliance requirements and data security concerns are accelerating growth of the privileged account management market.

5. Weigh the pros and cons of end-to-end encryption and tokenization.

Tokenization and end-to-end encryption have emerged as promising technologies, but both have benefits and drawbacks that organizations must weigh.

6. Learn how frameworks and technology can help your PCI DSS compliance efforts.

This mini-guide offers a variety of tips on how organizations can use several frameworks, technologies and standards to help manage PCI DSS efforts and ease the compliance burden.

Finally, focus on health care

… that is, if health care compliance is your responsibility.

If you work in healthcare, SearchSecurity.com published a helpful HIPAA compliance manual that will be useful for IT professionals entrusted with health care compliance. Included in the guide is a HIPAA compliance training, audit and requirement checklist, including advice on how to prepare for a security audit.

Here are several other useful stories and tips on health care compliance:

1. Personal health records not measuring up in privacy, say advocates

The federal government has called for greater use of personal health records as part of electronic health record systems. Advocates say PHRs fall short in data control, privacy and security.

2. Growing health information exchanges show lower costs, better care

Some health care organizations such as health information exchanges are showing improved efficiency, lower costs and better patient care using EHRs.

3. Encryption tops new rules of electronic health records compliance

When it comes to electronic health records and personal health information, secure storage can have many meanings, but only one that counts: Encrypt data as many ways as you can.

For more on HITECH and HIPAA compliance, also review:

Reblog this post [with Zemanta]


December 23, 2009  2:04 PM

Email to the Editor: Federal data breach law needs enforcement to work

GuyPardon Guy Pardon Profile: GuyPardon

Earlier this month, the U.S. House of Representatives passed the Data Accountability and Trust Act, H.R. 2221, the first step toward a comprehensive national data breach notification law. As I wrote in the news story, if the U.S. Senate can reconcile the bills proposed there with the House Version, a new federal data breach standard will emerge.

At least one reader wasn’t so sure, however, that any federal data breach notification law is worth the paper it’s printed on without enforcement:

“The point never discussed with this or any other law, process or procedure is that without assertive enforcement – active, visible and without remorse – this initiative will be of no more use than any of the others currently enacted. At best, a paper tiger. At worst, a smoke-screen that protects the guilty and places the innocent at even greater risk.

The concept of burying a problem under mountains of paper (or rhetoric) has long been demonstrated to be no answer to the issues and real dangers facing today’s and tomorrow’s world.”

-Ken Bumgarner, IWWIT, U.S. Consultant, Senior Systems and Security Engineer, Information Security Department, National Information Center, Ministry of Interior, Riyadh, Kingdom of Saudi Arabia

I’ve written in the past about enforcement of data protection laws, specifically with regards to the amended Massachusetts data protection law. The enforceability of a regulation is critical to its passage and success, as are meaningful penalties. Even more important, in this writer’s opinion, is the likelihood of that enforcement.

Thanks to Mr. Bumgarner for writing in.


December 22, 2009  9:55 PM

White House introduces Howard Schmidt as new cybersecurity coordinator

GuyPardon Guy Pardon Profile: GuyPardon

This morning, the White House made it official: Howard Schmidt will be the nation’s next cybsersecurity coordinator. The longtime industry veteran will be returning to the executive branch, where he worked previously as vice chairman of the President’s Commission on Critical Infrastructure Protection. Schmidt will report to deputy national security advisor (NSA) John Brennan. You can watch video of Howard Schmidt on the cybersecurity coordinator role by clicking on the image below:

Schmidt was formerly chief information security officer (CISO) at eBay and chief security officer at Microsoft and has worked with federal and local law enforcement and the Defense Department. As Ellen Nakashima reported in The Washington Post, the new cybersecurity coordinator also served as special adviser for cyberspace security from 2001 to 2003, where he shepherded the National Strategy to Secure Cyberspace, a plan that Nakashima writes “was largely ignored.” Schmidt was also the president and CEO of the Information Systems Security Association, an international nonprofit organization that focuses on risks and research in the cyberworld. The question now will be whether a man hailed as a good communicator can also ensure better cybersecurity across industry and government.

“Howard is a good match for this task,” said Vint Cerf, Google’s chief Internet evangelist, as quoted by The Atlantic Monthly’s Marc Ambinder. “I’ve been impressed by his consensus-building style. He’s thoughtful, knowledgeable and he knows Washington.”

Cerf, as quoted in the New York Times article on the cybersecurity coordinator, said that “I’ve come away with a strong sense that Vivek Kundra, chief information officer, and Aneesh Chopra, the chief technology officer, and participants at the N.S.C. are aligned on this effort.”

Filling the position at the National Security Council was overdue, given the time that has elapsed since Melissa Hathaway delivered a cybersecurity report that called for a cybersecurity coordinator to coordinate the nation’s efforts. As SearchSecurity.com Editorial Director Mike Mimoso reported, “Obama announced on May 29 he intended to personally select a cybersecurity coordinator who would coordinate cybersecurity policies across government agencies.”

In May, Threatpost Editor Dennis Fisher recorded a podcast with Schmidt. In the podcast, the incoming cybersecurity coordinator talks about the role, cybercrime and how to fix federal cybersecurity.

CSO Online Senior Editor Bill Brenner enjoyed excellent timing yesterday when he published an email interview with Schmidt. Schmidt made a number of predictions for 2010, including that he believed that cloud computing will be a security enabler. Schmidt wrote that “2010 will be the tipping point as to much wider adaption in all sectors. The overall net effect will give us a better chance to develop more security in the cloud using better vulnerability management/reduction, strong authentication, robust encryption and closer attention to legal jurisdictions.”

The timing of the White House appointment of a cyber coordinator is, as Ambinder wrote, something of an early Christmas gift, though perhaps not for Schmidt himself. As Ambinder observed, “It’ll be a thankless job: given the near-certainty that the government will experience some massive data breach or a major cyber terrorism attack, Schmidt will be both the point person — and the person seen as responsible, even though he lacks the statutory authority to prevent these catastrophes.”

In the security industry, reactions to the appointment have been generally positive. Like Ambinder, Dave Lewis, a Canada-based IT security practitioner and editor at Liquidmatrix Security Digest, also sees a tough challenge ahead for Schmidt. “I think that this is an extremely unenviable position for him to take,” he said. “There are numerous turf wars that he will be at risk of becoming collateral damage in the crossfire. I would like to see him succeed. There needs to be a central point of control for IT security.”

George Moraetes, an information security and enterprise architect, related a similar sentiment: “I really don’t know if congratulations or even condolences are in order.”

Moraetes supports the appointment of Schmidt, stating he “is the best advocate and most experienced individual to take on this incredibly difficult job that basically has no teeth or jurisdiction to preside over federal agencies. He is the only person capable of this job, having solid federal government and corporate experience at top levels, and knows the ropes.”

Patricia Titus, former CISO for the Transportation Security Administration and now CISO for Unisys Federal Systems, is similarly supportive. “He comes with exactly the type of credentials to rally the right people at the needed levels. His private- and public-sector background lends itself well to knowing who needs to sit at the table. There hasn’t been that level of IT credentials and security experience in a similar position before.”

Titus sees the position of the cybersecurity coordinator directly under the deputy NSA as “critical to the success of the position. The fact that John has publicly stated that Howard will have regular access to the president shows that cybersecurity is a national priority.” Schmidt will be charged with assessing and mitigating a complex mix of threats and authorities. ‘I think that all of us in cybersecurity look at the difference between compliance and verifiable security carefully. Are we spending too much time writing documents, versus in real-time monitoring of security controls? Howard’s role may be to address that from a policy standpoint, with regards to securing critical infrastructure, government websites and agencies.”

UPDATE:

“I’m cautiously pessimistic about anyone in that job, but I think Howard has a better shot than most,” said David Mortman, CSO-in-residence at Mason, Ohio-based security consultancy Echelon One. “Howard is a known quantity and knows how to play the game. Gives him a huge advantage, since it’s like he’s simultaneously an insider and an outsider. Hopefully the best of both worlds.”

Dan Kennedy, CISO of the Praetorian Security Group, also wrote in to share his take on the appointment of the new cybersecurity coordinator: “I am familiar with Howard, having watched him speak numerous times, being introduced to him a few times, having sat at a dinner round table across from him, and having been an ISSA member for years who reads his introductions every month. I think Howard Schmidt is both a smart guy and one who understands the issues of information security. I don’t always agree with what he has to say, but if you are quoted as much as Howard is that will happen. He doesn’t say completely crazy things, as a few senior security executives do now and then, and has a conservative approach to IS concerns. Howard is a competent choice, and clearly better than many alternatives having worked in the private sector and having been involved very closely and nearly exclusively in the infosec industry. This is much better than, say, a competent technologist, a lawyer who understands technology at a high level, or related choices taking on their first big information security job with this position.”

“That said, he is a safe choice, one who has had an opportunity already in what was a very similar position under the Bush administration. I, like many folks, wanted to be excited by the choice of cybersecurity czar, to see someone I thought would really shake things up. A safe choice doesn’t do that. I voted for Obama to make competent but also pushing the envelope decisions. I hoped for an appointment that would inject some discomfort into an established information security hierarchy in need of a change agent. Howard may be that; perhaps he wasn’t given enough of a chance or shackled by a lack of organizational power the last time around.”

“Don’t get me wrong: this appointment is a positive. There’s a more empowered position (especially now that the nonsense on reporting line is resolved) and a competent person in it helps information security. It was a long time coming. Howard is not afraid to speak uncomfortable truth to power, one of the hallmarks of a great CISO. I congratulate him and look to this appointment with optimism.”

Reblog this post [with Zemanta]


December 8, 2009  12:39 PM

Yahoo adds online privacy tool ahead of expected FTC compliance rules

GuyPardon Guy Pardon Profile: GuyPardon

FTC compliance now means new rules for social media marketing. By next year, FTC compliance could also mean ensuring that online advertising doesn’t violate tougher consumer privacy regulations — or even la

On Monday, Yahoo launched a new online privacy tool that, in theory, allows users to gain more insight into the data that the media company has gathered about their interests. According to the press release, the tool provides users with the ability to “assert greater control over their online experience,” providing Yahoo’s “educated guesses about their interests” and granular controls for those users to opt out of those categories or out of interest-based advertising entirely.

The “Ad Interest Manager” was announced and released in beta on the same day the Federal Trade Commission held its first roundtable on privacy in Washington, D.C. The privacy workshop agenda (PDF) for the FTC privacy roundtable includes academics, advocates and representatives from media, data mining, software and analytics companies.

This introduction of an online privacy tool for consumers by Yahoo follows the addition of an online privacy dashboard from Google last month and the July release of self-regulatory online privacy principles for the use and collection of behavioral data for Internet advertising.

Whether such efforts are enough to preemptively address attention from the FTC will be an open question in 2010. As FTC chairman Jon Leibowitz stated earlier in the year, this is “industry’s last chance to get its act together on behavioral targeting.”

Capitalizing on this regulatory focus, the Center for Democracy & Technology (CDT) also began a consumer online privacy campaign last week called “Take Back Your Privacy.”

“All social media should have granular privacy controls,” said Leslie Harris, president and CEO of CDT. An important element of the CDT’s online privacy campaign effort includes the release of an online privacy Compliant Tool that allows people to register online privacy concerns with the FTC and share that action with connections with social media.

Harris, who was at the FTC’s privacy roundtable yesterday, says that next year will be “the first time there will be serious consideration of consumer privacy legislation in many years.”

According to the CDT’s Ari Schwartz, Rep. Richard Boucher has put forward an outline of a consumer privacy bill that will be a framework for action in January.

As Kara Swisher pointed out at CNET, the addition of this online privacy tool by Yahoo coincides with a “bigger backdrop” of “the pending regulatory approval of the massive search and advertising partnership between Yahoo and Microsoft. The two companies announced last week that they had completed the definitive agreement for the deal.”

As Swisher observed, “one of the key issues for regulators, of course, is the privacy implications of combining the search and online ad technologies of the No. 2 and No. 3 players.” Google, Yahoo and the online advertising industry as a whole will be watching carefully to see what FTC compliance and action from Congress will mean for all in the year ahead.

For insight into the way that the regulator sees the relationships here, review the FTC graphic below describing a user’s “personal data ecosystem.”

A "personal data ecosystem"

[Image source at FTC.gov. (PDF). For specific industry relationships, review these data flow charts. (PDF).]

Reblog this post [with Zemanta]


December 1, 2009  5:10 PM

Enterprise log management crucial to better IT compliance

GuyPardon Guy Pardon Profile: GuyPardon

Compliance requirements have long since pushed organizations to adopt better log management. Like IT staff at public companies, where the Sarbanes-Oxley Act and log management go together like peanut butter and jelly, IT execs working in government have to retain, manage and store logs to comply with FISMA, the Federal Information Security Management Act.

Last month I moderated a panel on enterprise log management at the CA IT Government Expo in Washington, D.C. The two panelists were Jon Kim, security architect of GTSI Corp., and Joe Ford, CTO and vice president of professional services at Patriot Technologies.

Both men offered useful best practices and practical insight into the challenge of managing logs within the enterprise. When it came to distinguishing between log management and security event management (SEM), both men observed that the utility of SEM lay in monitoring for specific access issues. Identifying changes in access or usage patterns that could indicate an issue is a key component and capability of security information and event management systems. In this context, the importance of of keeping raw log data around for forensic analysis was clear.

Department of Defense (DoD) directives on log management are directly related to achieving better “situational awareness,” a much-used concept in the cybersecurity world. The DoD Information Technology Security Certification and Accreditation Process, or DITSCAP, includes groups of activities and tasks that must be performed over the lifecycle of any existing or upgraded DoD system that collects, stores, transmits or processes either unclassified or classified information.

Better automation and monitoring of logs has the potential to reveal issues across critical infrastructure, which is critical as threats emerge. Recently released Consensus Audit Guidelines specifically refer to the importance of tying identity to activity. Both panelists saw considerable maturation in this area of log management. The next challenge will be building better authentication into enterprise systems that more effectively interoperate with log management software. Security vendors are actively pursuing this goal.

The final question that the panel considered was the lack of clear guidance from the government on how long logs should be retained. Both men acknowledged the issue, referring to the National Institute for Standards and Technology (NIST) SP 800-53 document, which describes several controls related to log management, including the generation, review, protection and retention of audit records.

Both panelists suggested that best practices should be based on the risk profile for each organization and the potential relevancy of the information to audits. In the back and forth between the panel and the audience, it was also clear that considerable differences exist within the defense community on how much and how far back to retain.

Few network, security or compliance managers would dispute that log management formats and standards are in a state of flux. In fact, enterprise log management may be the least standardized area of IT. There are efforts under way to agree on common standards for logs, however. Earlier this year, the Open Group Security Forum updated its log standard, Distributed Audit Services, or XDAS. The Security Forum has also announced work on a new compliance standard, automated compliance expert markup language, or ACEML.

Standards aren’t the only challenge for enterprise log management. The sheer volume of log files generated across networks is a huge issue. As NIST offered in its SP 800-92 guidance on security and log management:

A fundamental problem with log management that occurs in many organizations is effectively balancing a limited quantity of log management resources with a continuous supply of log data. Log generation and storage can be complicated by several factors, including a high number of log sources; inconsistent log content, formats, and timestamps among sources; and increasingly large volumes of log data.

Best practices — and regulatory mandates — mean logs should be generated, archived and monitored regularly for insight into employee activity and to detect and prevent system outages and security breaches. Without effective enterprise log management and analysis, more organizations will be found noncompliant and remain at greater risk.


December 1, 2009  4:34 PM

IT governance, risk and compliance: Buzzword or not, GRC is relevant

GuyPardon Guy Pardon Profile: GuyPardon

As IT professionals log back in after the Thanksgiving holiday break, meeting regulatory compliance mandates continues to occupy significant amounts of both time and budget. The top regulatory compliance trends that affected IT this year have added more areas in which to manage risk and new challenges for reporting, all in the context of increased enforcement. IT governance, risk management and compliance software, or “GRC,” has been pitched by many vendors in suites that give IT compliance professionals better tools to manage processes, resources and reporting.

As senior writer Linda Tucci recently reported, IT is increasingly turning to enterprise risk management as uncertainty in the macroeconomic climate continues. Even as some enterprises have held off on further investments in GRC software, she observed, “the more budgets tightened, the more imperative it became that both IT and the business target their biggest exposures and eliminate redundant controls and audits.” For instance, in some areas, like carbon compliance, specialized GRC software has the potential to help turn carbon footprint management into cost savings.

Given continued interest in the potential of GRC software, we published a new governance, risk and compliance FAQ yesterday. If you know of neutral, useful governance, risk and compliance resources online that should be added to the FAQ, please let us know in the comments or by sending an email to editor@searchcompliance.com. As we add more resources to SearchCompliance.com, you’ll be able to find them at our IT governance, risk and compliance topic page. Also, make sure to check in throughout the week here on the IT Knowledge Exchange, which features two GRC blogs: “Regulatory Compliance, Governance and Security,” by Charles Denyer, and “IT Governance, Risk, and Compliance,” by Robert E. Davis.

Reblog this post [with Zemanta]


November 24, 2009  3:35 PM

IT compliance resources: Join our communities on Facebook and LinkedIn

GuyPardon Guy Pardon Profile: GuyPardon

As 2009 comes to a close, we know that the ways you are finding IT compliance resources, news and fellow compliance professionals are changing as the online environment evolves. We know your inbox isn’t the only place to find you. Last week, we created two new communities on Facebook and LinkedIn.

Facebook, Inc.
Image via Wikipedia

If you’ve been staying up to date with the activities of friends, family members and colleagues on Facebook, now you can keep up with IT compliance there, too.

Just become a fan of SearchCompliance.com on Facebook.

If you focus your social networking activity on connecting with colleagues, please consider joining our IT compliance group on LinkedIn.

And, as many of you may be aware, SearchCompliance.com has been active on Twitter since our launch in January. You can follow us there at @ITcompliance.

Regardless of the platform, you’ll find updates and discussions among fellow compliance and security professionals about our most recent news, tips, interactive content, e-books and more.

Reblog this post [with Zemanta]


November 20, 2009  4:15 PM

Former cyber czar describes cybersecurity policy-making, faults FISMA

GuyPardon Guy Pardon Profile: GuyPardon

How did the first U.S. “cyber czar” describe his time as the nation’s assistant secretary for Cybersecurity and Communications (CS&C)? Quoting Mark Twain, Greg Garcia observed that “a man who carries a cat by a tail learns something he can learn in no other way.”

It was “like a paintball fight in an Escher painting” at the Department of Homeland Security (DHS), Garcia described, “with great affection.”

Jokes aside, Garcia, who spoke at the CA IT Government Expo this week in Washington, was clear in describing what it was like in the crucible of the DHS making cybersecurity policy. “Our adversaries right now are better organized and better motivated than we are,” he said. “We, as a nation, are at an inflection point in this national cybersecurity challenge. We have a foundation for organizational structure in the private sector. We need to build a trust framework. If you don’t have an affirmation of trust, even with the same team, you’re not going to be able to get to an effective real-time response.”

Garcia, who served as assistant secretary for CS&C from 2006 to 2008, broke down the components of the Comprehensive National Cyber Security Initiative (CNCI) that President Bush signed in January 2008. The CNCI consists of 12 elements aimed at improving cybersecurity on federal networks. “We were seeing terabytes of data flowing out of .gov networks,” said Garcia.

CNCI components include intrusion detection and prevention, research and development into so-called “leap ahead” technologies and better situational awareness, coordinated through the National Cybersecurity Center.

Garcia advocated for better counterintelligence for cybersecurity, “classified network security,” perhaps referring to the Einstein monitoring tool and improved cybereducation and training.

Echoing the NERC CSO’s remarks last month, Garcia has had to think through how deterrence strategy changes in cyberwar, especially when other nation states are in the electric grid or government networks. “What point does a cyberattack become an act of war?” he asked. “How do you make it more dangerous for our adversaries to attack us? A lot of it has to do with attribution.”

Garcia affirmed the need for a Federal Information Security Management Act (FISMA) for ISPs, but said that “it needs to be market-driven, at least for now, until we can determine if there’s market failure. Every infrastructure sector has different business models and risk models.” Garcia provided what may be a controversial example: an initiative where major investment banks came together and “designed their own FISMA, if you will,” with auditors to assess financial network security.

When it came to the utility of FISMA in assessing cybersecurity readiness, however, Garcia had few kind words. “FISMA has not been successful, primarily because it has been a box-checking exercise,” he said. “It is not evaluating security. That’s a very hard thing to do, because you have different threat models and vulnerability environments.”

Reblog this post [with Zemanta]


Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to: