Security Database

Working on Common Vulnerability Scoring System v3 integration

Security Database Team — 2016-07-31T23:00:00Z

While working on Common Vulnerability Scoring System v3 implementation, we have to make choices.
Some of them are easy, other tricky. As we already say, CVSSv3 and CVSSv2 can be affected to the same alert, and we must keep CVSSv2 for SCAP needs, and simply because some alerts does not have CVSSv3 (old alerts).
We must propagate the right score (and only one per alert). We cannot deal with 2 scores like the NVD, our alerts are linked (see crosslinks demo)
Alerts CVSS scoring priority (...)

- SD Papers / Documentations, vDNA, Update

CPE Deprecated Dictionary integration

Security Database Team — 2016-06-28T20:38:43Z

This update is one of our biggest 'technical' updates. We will now fully handle the CPE Deprecated Dictionary made by NVD. Thousand lines of codes, tests, checks, re checks and more. Again, our data quality, but also our alerts, will be greater.
But what is "Deprecated CPE Dictionary."
It means that when a CPE is no more valid, we handle it automatically. We made the change in our database, for alerts, but also on your vDNA Monitoring pool. And, of course, we mail you when it impacts your (...)

- SD News / Update, vDNA, Documentations

And Prev? What does that mean?

Security Database Team — 2016-03-14T14:13:58Z

Some of our data providers use these small typo to explain that a vulnerability affects multiple products and specially “previous version” of a product.
For products like google chrome, we can understand that manually reference 3,000 chrome versions could be hard work. Nevertheless, data integrity is critical! For you, and our alerting system, it's a big miss. So we have worked hard to find an automated way to tag all versions of a product impacted by a vulnerability. It's starting today.
We (...)

- SD Papers / Documentations, Update

CVSS v3 and Updates

Security Database Team — 2015-07-06T12:30:59Z

It's been a year without posting, but not without work. Attentive user has found that we have put into production some changes, like CVSSv3, CPE search, and add some API. We also have added the possibility to change your monitoring email (Business and enterprise). And yes, we also have corrected some bugs ;) Let's now talk about them.
Common Vulnerability Scoring System v3 As you already may know, the Common Vulnerability Scoring System v3, also know as CVSS v3 is now available on First.org. (...)

- SD Papers / Documentations, Update, vDNA

Code improvement and security, from good to great!

Security Database Team — 2014-07-28T09:02:02Z

After the last big update, we have decided to go into maintenance mode and made some code cleanup and rework. Minor change for you, but big update for us.
First of all, we have rewritten our Session Management. It's really interesting that "Session Encryption" does not use a "standard" nor PHP a session option that encrypt into memory...
So we start to work on our own side. But, what encryption mechanism and what PHP module?
Some sites help us with an interesting benchmark between Mcrypt (...)

- SD Papers / Update

Customize your monitored Products by adding an Environmental CVSS vector

Security Database Team — 2014-06-18T13:09:45Z

Yes, it's done! Now, you an customize your monitored products and add, for each one, a CVSS Environmental Vector! But, wait! What is an Environmental Vector and what it can do for you? Simple, lower or higher the score of an Alert, based on YOUR Environment!
The basis Starting with the base, here is the definition of the CVSS Scoring system:
“CVSS is composed of three metric groups: Base, Temporal, and Environmental, each consisting of a set of metrics. These metric groups are described as (...)

- SD Papers / vDNA, Documentations, Update

58.000+ Nessus files integration and vDNA API update

Security Database Team — 2014-02-17T18:48:06Z

Our Team have integrated 61.240 NASL files, 58.288 Nessus exploits (without marked deprecated or empty) with 190.370+ cpes and 149.850+ "Security-database" References into our database. Integration is done automatically each day, without human interaction like usual. And off course, we have added them to each alert, alert History, CPE, Dashboard, API...
Like the last update, we have integrated Nessus Exploits into our database. Of course, we now display exploits information in each alerts (...)

- SD Papers / Documentations, vDNA, Update

vDNA update and Snort Rules integration

Security Database Team — 2014-01-20T08:00:00Z

Happy new year 2014! Our Team have integrated 30.000+ Snort Rules into our database and have improved our vDNA API. Integration is done automatically each day, without human interaction like usual Of course, we have added them to each alert, alert History, CPE, Dashboard, API...
Like our the last update, we have integrated Snort Rules into our database. Of course, we now display Rules information in each alerts and each CPE (Product or Version). At this time, 34 049 Snort Rules. As we (...)

- SD Papers / Documentations, vDNA, Update

vDNA Crosslinks as Christmas gift

Security Database Team — 2013-12-18T08:21:07Z

vDNA Crosslinks allows you to gather +80.000 Security Alerts data from Security-Database and export it as JSON format. Exports provide related Alert information. By that we mean, all alerts linked to the first one at specified depth.
We are proud to bring you our latest creation, vDNA Crosslinks. What alerts are linked to each other ? What is the vulnerability scoring propagation? We offer this information as JSON format and have built a demo website to play with, and perhaps, give you (...)

- SD Papers / vDNA, Update, Data Mining

CVE syntax is changing

Security Database Team — 2013-12-14T15:30:36Z

CVE syntax is changing on January 1, 2014. Be prepared, modify and test your code. This modification is not a big deal, the last 4 fixed digits became arbitrary digits with a minimum of 4 and without a maximum.
"The new syntax for CVE Identifiers (CVE-IDs), which was determined in a recent vote by the CVE Editorial Board, will take effect on January 1, 2014. This announcement is being made now so that users will have enough time to change their processes and software to handle the new ID (...)

- SD Papers / Documentations, Update