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: July 2015

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

Comments up and running again

Posted on July 28, 2015 by Code Curmudgeon
Just a brief public service announcement. After being made aware over the weekend that the comment system wasn’t working I’ve figured...
SysAdmin internal

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
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

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.
Man-in-the-middle
Man-in-the-middle (MITM) attacks are where a person or software sits in the middle of communication between two parties. For example between your computer and your bank. Web MITM attacks are often performed by self-signed root certificates where someone like a hotel or computer manufacturers certifies the identity of both parties without actually having the authority. Often this is done for advertising purposes to either monitor behavior or inject ads into a data stream. It also exposes any of the data that is supposedly securely encrypted, like your bank credentials.
security certificate
A digital artifact used in cryptography for secure connections like SSL. The certificate is used to authenticate who a user was, letting you know that you're dealing with the person you think you are. Certificates are normally issued by authorities who take steps to ensure identity before issuing any certificate. There are also self-signed certificates that you can create for yourself but do not have the same level of trust. In essence you are saying "I am who I say I am." For more details see wikipedia.
Phishing
A security attacked based on tricking you to put important data like your login and password into a fake website. For example, a faked email from your bank, even using the proper bank picture you're expecting. They tell you there has been a breach and you need to login immediately and change your password. Don't do it, go to the website directly and see if they have any message there. When in doubt, call the company.