nCircle.com >> nCircle Blog >> Sync

« New CISSP Requirements | Main | The iPhone, our new security nightmare »

Does your vendor help or hinder your security methodologies?

As security operations manager, one thing that concerns me is the ability to use vendor information within our risk management methodologies. Vulnerability and configuration compliance tools are important assets. The discovery tool allows a team to find vulnerable systems. Configuration tools permit us to set a standard, discover outliers and enforce new policies. Nonetheless, there is a missing component -- the vendor interaction and how it affects your resource planning and immediate risk management.

Already in 2007, we've experienced some interesting vendor dynamics, which have forced us to stretch our normal operational methods. FreeBSD recently froze its ports distribution tree in order to upgrade Xorg and its interdependencies. The freeze meant that even though port maintainers had submitted patched versions of PHP, our normal methods of software patching were hindered. With Apple, we saw a handful of Java and Quicktime interdependent bugs. In one case, a third party's suggestion was to disable Java. This mitigation method left many enterprises at an impasse -- disable Java and hinder work performance or accept the risk. April brought the remote DNS RPC bug from Microsoft. Even though this vulnerability didn't affect us, its what began my dive into these thoughts. What's a consumer to do when put in a position of a serious vulnerability without a clear mitigation or solution strategy?

When put in such a position with little information and no place to acquire assistance, we become dependent on our own skills and strategies. The decisions made are highly driven by the vendor's ability to provide assistance. The ad hoc rating system below was spawned by this dilemma. This is a comparison of Apple, Microsoft and FreeBSD. How do your vendors rank?

Item Reason Apple.png MS.png FreeBSD.png
Regular Bulletin Release Schedule ERP x.png check.png x.png
Security Announcement Mailing List Communications check.png check.png check.png
RSS Feeds Communications check.png check.png check.png
Email Cryptographically Signed Info Integrity check.png check.png check.png
Security Bulletin: Pre Announcement ERP x.png check.png x.png
Security Bulletin: Summary Communications check.png check.png check.png
Security Bulletin: FAQ Communications x.png check.png x.png
Security Bulletin: Mitigations Risk Mgmt x.png check.png check.png
Security Bulletin: Workarounds Risk Mgmt x.png check.png check.png
Security Bulletin: Update/Patch Risk Mgmt check.png check.png check.png
Security Bulletin: CVE Usage Interoperability check.png check.png check.png
Security Bulletin: CVSS Usage Interoperability x.png x.png x.png
Security Bulletin: Acknowledgments Communications check.png check.png check.png
Security Bulletin: Website Uses SSL Info Integrity x.png x.png x.png
Vendor Free Detection Tool Risk Mgmt x.png check.png check.png
Vendor SDLC Public Communications x.png check.png check.png
Alt Vendor Communication Forum Communications x.png check.png check.png

TrackBack

TrackBack URL for this entry:
http://blog.ncircle.com/cgi-bin/mt-tb.cgi/221

Listed below are links to weblogs that reference Does your vendor help or hinder your security methodologies?:

» The iPhone, our new security nightmare from Sync
Thanks to Andy Greenberg at Forbes for allowing me to interject some commentary into his article "is the iPhone Insecure?" While I... [Read More]

Comments (2)

Alex:

Security Bulletin: Mitigations
Security Bulletin: Workarounds
Vendor Free Detection Tool
Security Bulletin: Update/Patch


Not to be nit picky, but shouldn't these things be vulnerability management, not risk management?

Not a nit picky question. I used to think that there was a distinction. Vulnerability management is just one piece of risk management. I generally only make the distinction based on the audience at hand.

Post a comment

(If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear on the entry. Thanks for waiting.)

Verification (needed to reduce spam):

Bio

Blog: Sync
Author: Andrew Storms

As nCircle's Director of Security Operations, Andrew Storms is responsible for setting and enforcing the company's security compliance programs as well as overseeing day-to-day operations for the Information Technology department. He is a Certified Information Systems Security Professional (CISSP).

About

This page contains a single entry from the blog posted on June 1, 2007 6:43 PM.

The previous post in this blog was New CISSP Requirements.

The next post in this blog is The iPhone, our new security nightmare.

Many more can be found on the main index page or by looking through the archives.