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

Tag: appsec

Why We View AppSec Vulnerabilities As False

Posted on July 29, 2015 by Code Curmudgeon
I’d like to say a few things as a follow-up to my article on theoretical appsec vulnerabilities last week. The article generated some interesting...
Security appsec, cybersecurity, swsec, training

Unscientific AppSec Pain Poll

Posted on July 28, 2015 by Code Curmudgeon
Here’s another one of my completely unscientific polls – this time about AppSec. I find it interesting to know what others think about these...
Security appsec, cybersecurity, static analysis, swsec

Theoretical AppSec Vulnerabilities

Posted on July 23, 2015 by Code Curmudgeon
As you’re well aware cybersecurity and appsec incidents are a regular feature in the news. I try to avoid jumping immediately on the analysis...
Security appsec, cybersecurity, swfail, swsec

Closing the Barn Door – Software Security

Posted on October 23, 2014 by Code Curmudgeon
In the second part of my series on what we can do to contain and combat the recent rash of security breaches I’d like...
Security appsec, breach, cybersecurity, prevention, privacy, Security, static analysis
‹ Prev 1 2 3 4 5 Next ›
Categories
  • AI
  • Automotive
  • Business
  • Cloud
  • General
  • IoT
  • Journalism
  • Medical
  • Mobile
  • Open-source
  • Quality
  • Security
  • Software Development
  • Space
  • SysAdmin
  • Technology
  • Testing
  • Web
Latest Posts
  • Is AI Safe Enough for Safety-critical
  • 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 Does Everyone Hate Unit Testing
  • How is Open Source Different Than Legacy Code
  • Code Curmudgeon Coffee Mugs Now Available
  • Legacy Code: It's Not Just Old Code
Archives
  • April 2026
  • 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

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
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.
denial-of-service
Attackers try to make a computer, network, or application unavailable to end-users. For example by overloading it with too much traffic as in a distributed denial of service.
code review
Code review is a process where programmers look at each others code and evaluate it's fitness for the intended purpose. It can find mistakes in design and implementation beyond simple syntax problems and improve quality.
peer code review (code review)
Code review is a process where programmers look at each others code and evaluate it's fitness for the intended purpose. It can find mistakes in design and implementation beyond simple syntax problems and improve quality.
BASIC
Beginners All Purpose Symbolic Instruction Code. A programming language designed specifically for beginners.
static analysis
Any form of software analysis that can be done on the code without actually executing the code. Encompasses techniques like pattern-based analysis, metrics, code review, etc.