Product security covers quite a broad spectrum of knowledge areas within the realm of technologies applied to enable communications in this highly connected world. However, there is a natural tendency to first focus on the basic capabilities of the product itself. But later, questions arise such as “Is the product in operation vulnerable and if yes, what are the next steps to protecting against the vulnerability?” or “What can I do if I suspect a security issue with a product?” As much as one would like to sustain 100% immunity against any vulnerability or issue, events happen, inherent product weaknesses are discovered or new attack vectors and methods arise to expose ways to compromise a product’s operation or behavior. At Cisco, the people that rapidly converge on such occurrences or the potential for such occurrences are the Incident Managers (IM) who reside at the core of the Product Security Incident Response Team (PSIRT) within Security Intelligence Operations (SIO). I think it is fascinating how well this team seamlessly executes with the precision, efficacy, and timeliness on a day-in-day-out basis covering a large array of complex hardware, software, and technologies. The IM focuses on driving the underlying processes around the discovery of security disclosures and issues related to Cisco products and networks. I hope you will find that this article provides you with an informative and personal perspective on the IM role that is integral to the ongoing efforts essential to protecting the Cisco customer.
On June 6-7, the National Institute of Standards and Technology (NIST) co-hosted a conference focused on HIPAA, the foundational U.S. health care information law. I attended the conference and came away with the sense that a) health care entities have begun to see clarity in the things they must do from an IT perspective to abide by the law’s requirement to protect patient information and b) they are motivated to do so through Federal moves to enforce the law.
The links between vague laws and concrete technical requirements to support them are usually ambiguous because the laws are written by non-technical lawyers and they often turn over implementation details to government departments.
This month marks the 63rd anniversary of the publishing of the novel Nineteen Eighty-Four, it might be interesting to take a look at what is currently the primary method used for tracking on the Internet, the Browser Cookie. Browser cookies are a subject with almost as much misinformation floating around as there is correct information.
Cisco is a Leader in the 2012 Gartner Wired & Wireless Magic Quadrant with a Policy-Guided Approach to Today’s Networks
In the past few years a number of paradigm shifts have made policy-based networking essential to effective enterprise IT management. Some of these shifts include an increased reliance on virtualization and the cloud; the “consumerization” of business networks that has occurred with the popularity of devices such as tablets and smartphones; and the rapid adoption of video in business communications. By applying appropriate policies within the network, IT managers can do a better job of meeting users’ expectations and become business enablers.
We believe our message of One Policy, One Management and One Network has been recognized in the recent Gartner 2012 Wired and Wireless LAN Infrastructure Magic Quadrant, where Cisco has been positioned as a leader.
Foundational to Cisco’s One Policy strategy is the Cisco Identity Services Engine (ISE), which enables organizations to create and deploy unified policy to address the need for BYOD compliance. ISE enables one consistent policy across the entire enterprise, as well as enforcement by correlating a unique combination of contextual information including user, device, location and time.
I recently traveled to the annual Gartner Security & Risk Management Summit in lovely National Harbor, Maryland with over 2,000 IT Security executives. There was a lot of buzz around Secure BYOD (bring your own device), and most of the major security vendors (including Cisco who I represented) had a story of some sort. Amidst this BYOD buzz, during a session, a man rose his hand and said:
“There is SO much talk about BYOD but I have not heard the industry definition, is there one? It seems it has many meanings to organizations struggling with it and to vendors trying to respond to it.”
This is a very fair question and remark. Most see BYOD as people bringing their own personal device to the office with access to all work-related applications while using it for personal life. Some organizations may say they do NOT have a BYOD policy because they only allow corporate sanctioned devices, but one could argue that is a BYOD policy that says “no personal devices”. A significant take-way was email is still the killer application for organizations to be mobile. I’m not sure my teenage daughter will agree with that, but she is not working for anyone yet.
Although all mobile devices are open to threats, it seems some may be more vulnerable than others -- such as Android devices with the OS fragmentation and a more open application store then Apple IOS devices. Further discussions with attendees suggested that there are many stakeholders in crafting the BYOD policy from HR, legal, networking, marketing & sales, and many times IT security is not brought to the table early enough. This can make the BYOD effort even more confusing for the IT security professional. Policy is the common ground for stakeholders to align. Once policy is determined, the network becomes the best vector to set and enforce it with both visibility and control. Russell Rice, Director @ Cisco spoke about the value of a policy-governed network in a standing room only session. You can view his presentation below, and read the white paper on the topic: