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

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

Edgescan and Huawei - Cybersecurity - Irish Times Article and Panel Discussion

By -
Image
I recently was interviewed by the Irish times on why is everything getting hacked and how can we change the game.... https://www.irishtimes.com/special-reports/cybersecurity-focus/criminals-have-an-inbuilt-advantage-in-the-great-cyber-arms-race-1.4651078  A recording of the Panel with Andy Purdy, CSO of Huawei North America. https://www.youtube.com/watch?v=cQJ1uSQ4IEk&t=33s Both are decent and worth a listen.
Read more

How Simple can it be.....XSS Prevention....

By -
Cross Site Scripting is sill a very common web vulnerability. Generally it is used to attack clients/users. It can be used for malware upload, botnet hooking, keylogging, a payload delivery system for clickjacking and CSRF attacks and much much more, all for 6 easy payments of $9.99...sorry got carried away there :) But is is easily preventable. You dont even have to know what XSS (type 0, type 1, type 2, DOM, Stored, Reflected) is to prevent it. One pretty simple way to prevent XSS is to use the OWASP ESAPI (Enterprise Security API). A very easy tool to use/invoke. It's also managed and attended to by Chris Schmidt ....A great guy... Regardless of what it does....if there was a mandate to use it on all redisplayed external input a site could become virtually XSS free!! (all for 6 easy payments of......). It's easy to deploy.... 1. Include in JSP (Java version) 2. Invoke in JSP 3. Job done!!! We include it by <%@ page import="org.owasp.esapi.ESAPI...
Read more