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

Category: Security

Security related issues.

IoT Security – A Contradiction in Terms

Posted on November 10, 2015 by Code Curmudgeon
The internet of things aka IoT has become the internet of hacks. More and more devices are being internet enabled. While this makes many...
Security appsec, cybersecurity, Hacking, iot

Halloween Security Slashers Webinar

Posted on October 28, 2015 by Code Curmudgeon
I’m doing a Halloween themed Parasoft webinar this Friday on Stopping Software Security Slashers with Static Analysis. As always it’s a free webinar and...
Security appsec, cybersecurity, static analysis, swsec

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
‹ Prev 1 … 4 5 6 7 8 … 12 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

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.
IAST
IAST is interactive application security testing. It's also been known variously as hybrid security testing, gray-box, and glass-box. This technique blends the inside-out approach of SAST with the outside-in approach of DAST to give you deep code-level visibility of a running application while it's in a real running state. This helps reduce false positives but still has the thoroughness limitations of black-box techniques in that it's only as good as the test suite being run in terms of coverage.
DAST
DAST tests an application for security vulnerabilities by monitoring and probing an application while it is actually running - thus the dynamic test. DAST starts from inputs and is a black-box or external view. This gives is a very realistic view of application behavior, but is difficult to be completely thorough. Penetration testing or pen-test is a common form of DAST.
SAST
SAST is security testing that is done on source, byte-code, or binaries but without actually executing them - thus the "static" testing. Typically this includes things like software metrics, static code analysis and even peer review. SAST provides a white-box or inside view to the application. It can both find possible vulnerabilities and weaknesses by looking for anti-patterns as well as enforcing secure software engineering standards by looking for proper patterns.