Liability in cybersecurity

Both the government and its contractors need to secure sensitive data.

It looks as if federal officials are finally starting to take notice of how governmental computer networks in the United States are attacked thousands of times a day. For the first time, the Pentagon is forming one central command to prepare for the future of computer warfare. This new command will concentrate on protecting information in the public sector and focus on keeping the information transfer between governmental agencies and private companies secure. The central command is absolutely necessary for a country that is the engine of the global information machine. The nationâÄôs cybersecurity has been unorganized at best. According to a recent article by The New York Times, a total of four commands handled threats with little protocol to follow. These sloppy procedures led to unsecure governmental networks, leaving sensitive data in jeopardy. Information ranging from social security numbers to multi-billion dollar governmental transactions were all exposed because of a security protocol that was simply inefficient at all levels. The federal government should consider even more alternatives when working with the public sector. In a recent cyberspace review, current acting Senior Director for Cyberspace Melissa Hathaw ay recommended that the government use tax incentives to leverage the private sector to implement rigorous security protocols when working with governmental information. Technology companies have created their own security protocols because of little government regulation. While companies are certainly capable of creating their own security procedures without intervention, they must be forced to take liability and take the fallback if they fail to fully secure sensitive information. Federal officials must realize that a lack of diligence will continue to shadow sensitive governmental information unless liability is rightfully allocated to the companies responsible for securing this sensitive data.