2019-013-ASVSv4 discussion with Daniel Cuthbert and Jim Manico - Part 2
Published April 7, 2019
56 min
    Add to queue
    Copy URL
    Show notes


    SpecterOps and Tim Tomes are giving training at WorkshopCon https://www.workshopcon.com

    Rob Cheyne Source Boston - https://sourceconference.com/events/boston19/

    Austin Cybernauts meetup - https://www.eventbrite.com/e/cybernauts-ctf-meetup-indeed-tickets-58816141663


    Architecture is not an implementation, but a way of thinking about a problem that has potentially many different answers, and no one single "correct" answer.


    “is to normalize the range in the coverage and level of rigor available in the market when it comes to performing Web application security verification using a commercially-workable open standard. “


    #ASVS team:

    • Daniel Cuthbert @dcuthbert
    • Andrew van der Stock
    • Jim Manico @manicode
    • Mark Burnett
    • Josh C Grossman







    https://www.owasp.org/images/3/33/OWASP_Application_Security_Verification_Standard_3.0.1.pdf - old version

    http://traffic.libsyn.com/brakeingsecurity/2015-046_ASVS_with_Bill_Sempf.mp3  - Older BrakeSec Episode


    ASVS Page 14 - “If developers had invested in a single, secure identity provider model, such as SAML federated identity, the identity provider could be updated to incorporate new requirements such as NIST 800-63 compliance, while not changing the interfaces of the original application. If many applications shared the same security architecture and thus that same component, they all benefit from this upgrade at once. However, SAML will not always remain as the best or most suitable authentication solution - it might need to be swapped out for other solutions as requirements change. Changes like this are either complicated, so costly as to necessitate a complete re-write, or outright impossible without security architecture.”


    What are the biggest differences between V3 and V4?

    Why was a change needed? 

    https://xkcd.com/936/ - famous XKCD password comic

    David Cybuck: Appendix C:  IoT

        Why was this added?

        These controls are in addition to all the other ASVS controls?

    How do they see section 1 architecture and section 14, configuration --- in the context of rapid deployment, infrastructure as code, containerization.


    You added IoT, but not ICS or SCADA?



    BrakeSec IoT Top 10 discussion:




    Seems incomplete… (Section 1.13 “API”)

        Will this be added later?

        What is needed to fill that in? (manpower, SME’s, etc?)


    3 levels of protection… why have levels at all?

        Why shouldn’t everyone be at Level 3?

        I just don’t like the term ‘bare minimum’ (level 1)--brbr


    Threat modeling blog (leviathan): https://www.leviathansecurity.com/blog/the-calculus-of-threat-modeling

    Adam Shostack ThreatModeling Book: https://www.amazon.com/Threat-Modeling-Designing-Adam-Shostack/dp/1118809998



    Cost to get to L2? L3?

    https://manicode.com/ secure coding education



    Check out our Store on Teepub! https://brakesec.com/store

    Join us on our #Slack Channel! Send a request to @brakesec on Twitter or email bds.podcast@gmail.com

    #Brakesec Store!:https://www.teepublic.com/user/bdspodcast



    #Youtube Channel:  http://www.youtube.com/c/BDSPodcast

    #iTunes Store Link: https://brakesec.com/BDSiTunes

    #Google Play Store: https://brakesec.com/BDS-GooglePlay

    Our main site:  https://brakesec.com/bdswebsite

    #iHeartRadio App:  https://brakesec.com/iHeartBrakesec


    Comments, Questions, Feedback: bds.podcast@gmail.com

    Support Brakeing Down Security Podcast by using our #Paypalhttps://brakesec.com/PaypalBDS OR our #Patreon


    #Twitter@brakesec @boettcherpwned @bryanbrake @infosystir

    #Player.FM : https://brakesec.com/BDS-PlayerFM

    #Stitcher Network: https://brakesec.com/BrakeSecStitcher

    #TuneIn Radio App: https://brakesec.com/TuneInBrakesec

        0:00:00 / 0:00:00