Code Curmudgeon
Facebook Twitter Linkedin Youtube Instagram

Main menu

Skip to content
  • Home
  • SQLi Hall-of-Shame
  • IoT Hall-of-Shame
  • Security Resources
  • Books
  • Glossary
  • Other Articles
  • About
    • Photography
    • Privacy Policy

Monthly Archives: November 2019

CWE Top 25 2019 and On the Cusp

Posted on November 21, 2019 by Code Curmudgeon
The CWE Top 25 has been updated for 2019. It’s the first change to this important list of cybersecurity issues since 2011. They also...
General, Security appsec, cybersecurity, Security, swsec

Why Do You Hate Unit Testing

Posted on November 18, 2019 by Code Curmudgeon
You hate unit testing… you know you do. And you think that’s OK because everyone you know hates it too. You’ve tried it, you...
Software Development, Testing Agile, best practices, devops, Software Development, testing, unit testing

How is Open Source Different Than Legacy Code

Posted on November 13, 2019 by Code Curmudgeon
While preparing for a webinar about static analysis the other day, I was discussing the attributes of legacy code and it occurred to me...
General, Open-source, Quality, Software Development legacy, open source, opensource, quality

Code Curmudgeon Coffee Mugs Now Available

Posted on November 13, 2019 by Code Curmudgeon
I’ve finally broken down and started selling merchandize on Zazzle. At the moment it’s just a couple of coffee mugs, but there will be...
General
1 2 Next ›
Categories
  • AI
  • Automotive
  • Business
  • Cloud
  • General
  • IoT
  • Journalism
  • Medical
  • Mobile
  • Open-source
  • Quality
  • Security
  • Software Development
  • Space
  • SysAdmin
  • Technology
  • Testing
  • Web
Latest Posts
  • Using Agile and AI should be your New Years Resolution
  • How to know when you need SBOM
  • AI Ethics and the Three Laws of Robotics
  • Do AI Ethics Really Matter
  • CWE Top 25 2019 and On the Cusp
  • Why Do You Hate Unit Testing
  • How is Open Source Different Than Legacy Code
  • Code Curmudgeon Coffee Mugs Now Available
  • What is Legacy Code Anyway?
  • Can a word fix our cybersecurity problems
Archives
  • February 2025
  • February 2021
  • January 2020
  • December 2019
  • November 2019
  • October 2019
  • August 2019
  • July 2019
  • January 2019
  • September 2018
  • May 2018
  • October 2017
  • August 2017
  • June 2017
  • February 2017
  • January 2017
  • September 2016
  • August 2016
  • April 2016
  • March 2016
  • February 2016
  • December 2015
  • November 2015
  • October 2015
  • July 2015
  • March 2015
  • January 2015
  • October 2014
  • August 2014
  • July 2014
  • June 2014
  • April 2014
  • February 2014
  • January 2014
  • October 2013
  • September 2013
  • August 2013
  • June 2013
  • May 2013
  • March 2013
  • February 2013
  • January 2013
  • December 2012
  • September 2012
  • August 2012
  • July 2012
  • June 2012
  • May 2012
  • April 2012
  • March 2012
  • February 2012
  • January 2012
  • December 2011
  • November 2011
  • October 2011
  • September 2011
  • August 2011
Popular Posts
  • What Went Wrong with Static Analysis?
  • Theoretical AppSec Vulnerabilities
  • SQL Injection – When Will We Learn?
  • I Am Positive It Is False
  • Hacking: Medical Devices
  • Remembering a friend and luminary
  • What Does Static Analysis Have To Do With DevOps
  • ASQ Conference in Long Beach
  • SCA is the Latest AppSec Silver Bullet
  • Java Memory Settings – JVM Heap Size
© Code Curmudgeon

Definitioner

NVD
US National Vulnerability Database is a repository of known security issues in software, devices, systems, etc. Each issue can be linked to a CVE. Data is stored in a common format called SCAP to enable easy automation in order to update notification of needed patches and other remediation. See https://nvd.nist.gov/
CVE
CVE stands for "Common vulnerabilities and exposures" and is a way to define a particular security vulnerability in application, system, device, etc. Each security problem gets a unique CVE identifier and is listed as well in the NVD registry. Additionaly, sometimes further efforts can be linked to the underlying issues in application code itself, and will associate the CVE with particular CWE IDs. See https://cve.mitre.org
CWE
CWE stands for "Common weakness enumeration" and is a way to define a particular security issue in programming code. CWE is a security effort lead by the US government and industry to define a taxonomy for coding problems that lead to security vulnerabilities. Each vulnerability reported has an CVE ID and should be linked to the underlying CWEs that lead to the issue. There are currently approximately 800 items defined in CWE and efforts are underway to map their technical impacts to what kinds of problems the weakness may cause, as well as ISO 27010. CWE is often known for it's CWE Top 25 and On the Cusp lists of the most common software security problems. See https://cwe.mitre.org
vulnerability
This is a tricky word, especially in application security or cybersecurity. The simple definition in a software context is that the code has some problem that could be exploited by someone at some point. Some think of it as a piece of code with a proven exploit, IE a static analysis violation with a stack trace and values used. This is a very narrow definition that probably doesn't help improve the state of the art. I prefer the idea that it's code that is exploitable based on the body of knowledge (as encapsulated in software coding standards).
CAN (Controller Area Network)
Controller Area Network aka CAN aka CAN Bus is a wiring standard for vehicles that enables communication between various components and devices without having a host computer. For example doors, brakes, transmission.
IoT (Internet of Things)
common devices that have been internet enabled in order to remotely monitor and manage them, or collaborate with other devices, or provide extra functionality by accessing the internet. Like an internet enabled thermostat that you can control with your smartphone - see the Nest from Google.