AppSec and Secure By Design

AppSec and Secure By Design

The US Cybersecurity and Infrastructure Security Agency (CISA) has been a leader in a global movement to promote software that is "Secure by Design". I'd like to explore the role application security (AppSec) as produced by Checkmarx has with Secure By Design.

Software design begins with requirements. It is not uncommon in the race to get into the market, that a developer either ignores the security requirements, or doesn't make the effort to even articulate the security requirements. We as an industry has learned the hard way that retrofitting security into a fundamentally flawed system is hard. It isn't necessarily impossible, but it is generally hard and less likely to provide you the same level of security had you designed the system differently.

Back to design. In general for software it the combination of building custom code along with integrating dozens of third-party components or systems into something coherent and usable by the end customer. This is a complex process, often filled with trial and error. Often you won't know if something will work until you put it together. CISA and others are trying to influence this through the Secure By Design principals:

  • Take ownership of the customer security outcomes
  • Embrace radical transparency and accountability
  • Lead from the top

Through these principals there is hope that software developers will produce more secure software which is resilient to most cyberthreats, thus decreasing the chance of compromise and increasing the complexity and difficulty of the attack.

Having a well thought out AppSec program supports all of these principals. Reducing the threat surface of your application certainly impacts the customer security outcomes. If you have ever looked at a software-bill-of-materials you can appreciate what radical transparency looks like. At the heart of leadership is setting the priorities and security requirements for the software and the entire AppSec program.

So AppSec doesn't define the requirements or design the application, but is a critical set of tools for the developer to enable their goal of efficiently producing secure software. The world's developers are moving towards more and more automation, and AppSec tools are moving with them to enable automated testing within their existing CI/CD environment. Ideally a developer can leverage AppSec tools to automate the testing of their application security requirements.

Ideally it all starts at the beginning of the design process with the developer keeping those three Secure By Design principals in mind as they draw that first network diagram on the napkin in the airport bar. Even the best designed system will still require testing.


To view or add a comment, sign in

More articles by John Allison

  • FedRAMP 20x

    Today, the FedRAMP Program Office (PMO) released a blog post (FedRAMP in 2025 | FedRAMP.gov) outlining the changes they…

    2 Comments
  • Notes from CMMC and Small/Medium Businesses Webinar

    Today I participated in a webinar titled “CMMC Compliance Mid-Sized Contractors Can Afford”, hosted by our friends at…

    2 Comments
  • FedRAMP's "Program" Possibilities

    One of the most exciting aspects of the updated guidance on FedRAMP coming from the Office of Management and Budget…

    3 Comments
  • Big Changes to FedRAMP Coming

    Today, the Office of Management and Budget (OMB) released a much-anticipated update to the FedRAMP program. While much…

    9 Comments
  • Incomplete Cybersecurity Strategy

    The Government Accounting Office (GAO) just release an interesting blog post: In the blog post, the GAO breaks down the…

  • Indeed a Journey

    I am delighted and proud to announce that Devo has finally achieved FedRAMP authorization. While I was not with Devo at…

    11 Comments
  • Material Determination – The Role of Application Security

    The US Federal Securities and Exchange Commission (SEC) new Cybersecurity Disclosure rules came into effect today. This…

    1 Comment
  • Thoughts on the FedRAMP Advisory Board's Key Challenges and Takeaways

    First of all, I want to thank the FedRAMP Advisory Board for their first publication (that I know of) that goes into…

    1 Comment
  • Cybersecurity Strategy and FedRAMP ... A Vision of Singularity

    It has now been 10 days since the White House published the National Cybersecurity Strategy (you can find it here). Now…

    3 Comments
  • Armis Achieves FedRAMP Ready Status

    We did it! After a lot of very hard work, Armis has achieved FedRAMP Ready Status. I am so proud of the team.

    6 Comments

Insights from the community

Others also viewed

Explore topics