10 Rules for Vulnerability Management

By -



Rules for Vulnerability Management
Below is a list of items and requirements based on client discussions in the case of delivering decent vulnerability management to clients both big and small. 

 From Visibility to API integration, from Validation to Developer support the items below are what you should consider when deploying a vulnerability management program.

 1. Coverage is king, Both depth, Breadth and Frequency.  Both authenticated and public.

 2. Full stack vulnerability intelligence is key as "Hackers don't give a Shit" where your vulnerability is at.

 2. Keeping pace with development. As change occurs, vulnerability management should detect and assess the changes. DevSecOps / Development pipeline Integration is required.

 3. False Positives are an evil waste of time even if handled by automation. - Validation is important.

 4. False Negatives are evil-er. - Scanner tuning is important so we don't miss anything.

 5. Situational Awareness is required. Alerting and custom events are key to knowing what matters & when.

 6. API's are expected and required so we can automate, invoke, integrate & consume

 7. Visibility is key - Asset profiling is paramount. Whats my attack surface?

 8. Developer support is paramount. Vulnerability management is as much about mitigation as it is discovery.

 9. Vulnerability Metrics are required to help improvement: Peer relativity, Time-to-fix, Vulnerabilities by type, layer, risk are all important.

 10. Asset Categorization, Tagging, Vulnerability Risk Acceptance and Retesting on demand are required.



Comments

Post a Comment

Popular posts from this blog

Edgescan, why we do what we do.....

By -
Image
  The cyber security industry is full of solutions to make you more secure. Some are unproven and other approaches work if deployed properly. Our industry is very fragmented. for example a recent "Cyber Defense" award I noticed has 195 categories!  I suppose we need to ask ourselves as companies from time to time why we do what we do?  So, the following post is, I guess, the reason we developed Edgescan and why we believe its a decent solution to help organizations improve and be more resilient in relation to cyber security and system protection.... Vulnerability scanning alone did not work. The idea of software testing software for vulnerabilities is a good one but both sides of the equation may have bugs. Bugs in one side (The target) may result in vulnerabilities, whilst bugs on the other side (Scanner) may result in false negatives and false positives.  Accuracy : To that end we built edgescan as a combination of automation to discover vulnerabilities at scale but  when c
Read more

20 years of Vulnerability Managment - Why we've failed and continue to do so.

By -
Image
Cyber Security: Keeping Pace with Change. Getting breached can really ruin your day. Actually it normally happens on a friday evening as you are about chill for the weekend. The cause of must breaches is not rocket science, its more to do with the poor approach we have accepted because we underestimate the threat actor.  - An attacker does not scan your website/network once a quarter with a commercial or open source scanner or perform an annual penetration test against your systems to see if there is any low hanging fruit, so how do we expect to defend against such an advisory using that approach? Systems change now more frequently than ever due to the ease of cloud deployments and the speed of software deployments due to iterative development techniques. The rate of change increase results in exposures quickly manifesting and the organisation not even being aware of the exposure in the first place. Many organisations dont know what they have exposed on the public Internet. We need t
Read more
By -
Image
The HSE Data Breach and the State of Irish Cyber Security Many years ago, shortly after I founded the Irish chapter of OWASP ( http://www.owasp.org ) (in 2007??) we were delivering free application and software development classes to anyone who wanted them. It was a local low key affair but every class we delivered was "sold out". We have 60-80 folks mostly developers willing to spend 4-5 hours on learning the fundamentals of secure application development and testing. I suppose we felt cyber security was an important issue because that's what we did. At the time many folks in business felt cyber security was an overhead or a "tax" and did not give it much time. A few years later (late 2010) when the the foundation of the NCSC (National Cyber Security Centre) was announced, a few of us (local OWASP Ireland leaders) wrote a number of emails to the Irish government offering free cyber security training. As we were working for a non profit (501.3c) charity (OWA
Read more