Logical Writing Solutions, Inc.
  • Home
  • About Ann
  • About Us
  • Why Us
  • Deliverables
  • Case Studies
  • Blog
  • Fav Quotes
  • Contact

OUR BLOG

Defending Web Applications in an Agile Age

8/18/2017

1 Comment

 
By Ann Grove, Logical's President

​In agile environments where software changes are released at a hectic pace, many organizations believe it no longer makes sense for a security team to focus primarily on looking for security weaknesses late in the development process. That approach is costly and sometimes forces the delay of a release. Instead, agile teams want to better integrate the security function early in development.


But how? That was the question that Zane Lackey (@zanelackey) addressed today at an OWASP Philadelphia (@phillyowasp) event. Lackey is Chief Security Officer at Signal Sciences, the security monitoring and defense company he founded. His past roles include Director of Security Engineering at Etsy.

With agile, release cycles are "orders of magnitude" faster than they were a few years ago, Lackey noted. Pre-agile development models such as waterfall typically yielded a release every 12 to 18 months, whereas agile shops may release code several times a day, he said.
At this pace, “security is successful only if it is baked into the Dev/DevOps process,” Lackey said.

Below, we will walk through Lackey's top recommendations on securing web applications in agile environments: 
  • Integrate security into design with static analysis
  • Provide continuous security feedback through penetration testing and a bug bounty program
  • Increase the visibility of security within the organization by detecting attacks early and tracking/refining vulnerability and incident responses
Security Writer, Technical Writer, Technical Writing Jobs, Virginia, DC, Washington, Cybersecurity, Cyber Writings, Security Writing, Security, Documentation Specialist, Technical Communication, Tech Writer, District of Columbia, DC, D.C., Washington, Maryland, Baltimore, Virginia, Massachusetts, New York, NYC, NY, Hagerstown, MD, Maryland, Roanoke, Lynchburg, VA, Virginia, Richmond, Petersburg, Norfolk, Portsmouth, Newport, News, Newport News, MD, Baltimore, Salisbury, MA, Mass, Springfield, Mass., Holyoke, Boston, Manchester, NH, Providence, Rhode Island, RI, New Hampshire, New Bedford, Burlington, VT, Plattsburgh, Albany, Schenectady, Troy, Binghamton, Utica, Syracuse, Rochester, Buffalo, Technical Communicator, Technical Author, Tech Writer, Technical Content Developer, Content Developer, Content Designer, Information Developer, Technical Information Developer, Information Architect, Information Engineer, Information Designer, Documentation Specialist, Document Management Specialist, Documentation Manager, Text Engineer
Employ Security by Design with Static Analysis

A static analysis tool is a debugging tool that examines code for known issues without executing an application. Typically, static analysis is run on a designated frequency such as weekly or monthly.

To implement static analysis, Lackey recommends beginning with classes of vulnerability that are the easiest to address. This also demonstrates to the organization that static analysis can deliver both value and velocity. The analysis tool should be “tuned” for each class to eliminate most false positives before moving onto the next class, Lackey says, rather than attempting to tune all classes at once. For instance, a team can start with command execution and later move on to XSS, SQLi, Directory Traversal, etc.

In addition, rather than instituting automatic blocking to prevent disallowed primitives, Lackey recommends talking to developers. Through conversation, the security team can learn what a developer is attempting to protect and discuss how that can best be accomplished through hashing, encryption, file system operations, or another method. 
Finally, Lackey recommends building proactive alerting so that leaders are advised when sensitive or rarely changed portions of the codebase are modified. He suggests alerting development and security engineers to changes to key platform protections, rather than blocking so that approvals are not needed during an emergency. For instance, a team can establish an alert for a hash change on key files, authorization of primitives, session management, encryption wrappers, etc. This provides accountability without impacting velocity. 

Provide Continuous Feedback with Penetration Testing and Bug Bounties

Lackey discussed two primary sources of security visibility: penetration tests and bug bounty programs. 

Penetration testing (pen testing) was “real-time enough when software was released every 18 months,” Lackey said. The purpose of pen testing in organizations with bounties has shifted; the value of pen tests now is that they are more directed.

Many organizations augment pen tests these days with bug bounty programs which provide truly real-time and continuous feedback. Through bounty programs, organizations compensate or reward external volunteer testers for finding weaknesses or bugs in the product being tested. The emergence of bounty platforms such as HackerOne and Bugcrowd make bounty programs more manageable, for instance for international payments, Lackey said.

Increase Security Visibility 

To increase security visibility, Lackey recommends developing capabilities to detect attacks as early as possible in the attack chain. This is especially important when a bounty program is planned, in case a bounty hunter discovers a bug that he or she decides not to report, Lackey said. The hunter could decide to sell the bug to hackers or use the bug for a live exploit later. 

In addition, organizations should continuously test and refine their vulnerability and incident response processes and mature their forensic capabilities.

Conclusion

Organizations realize it is no longer feasible for security teams to primarily focus efforts late in development when discovered bugs are costly and may delay scheduled releases. Security teams in agile environments are increasingly participating in the early phases of web application development and are collaborating with, educating, and empowering developers. Even in fast-paced agile environments, secure development is possible with techniques such as integrating security into design, providing continuous security feedback, and making security visible, Lackey said.​

We can move faster than attackers for the first time.
~ Zane Lackey, Chief Security Officer, Signal Sciences
About Ann
Ann Grove is a Certified Information Privacy Professional and security enthusiast with 15+ years of writing experience.
1 Comment
The Sidiudai link
10/25/2023 01:28:53 am

Good reading this postt

Reply



Leave a Reply.

    BLOG POSTS

    All
    Advanced Persistent Threats
    Defending Agile Web Apps
    Dilbert: Acronym Madness
    Goals That Inspire
    Hacking The Family Car
    Launching An InfoSec Career
    Learning: Gamification
    Practical Threat Modeling
    Preparing For External Content Developers
    Privacy: Search History
    Sandboxed Web Browsers
    Top Security Podcasts
    User Stories
    Why White Papers Fail

    Archives

    October 2020
    March 2019
    February 2019
    January 2019
    August 2017
    June 2017
    March 2017
    February 2017
    July 2016
    May 2016
    January 2016
    March 2015
    March 2014
    July 2012

    RSS Feed

​© copyright 2024 Logical Writing Solutions
  • Home
  • About Ann
  • About Us
  • Why Us
  • Deliverables
  • Case Studies
  • Blog
  • Fav Quotes
  • Contact