DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports Events Over 2 million developers have joined DZone. Join Today! Thanks for visiting DZone today,
Edit Profile Manage Email Subscriptions Moderation Admin Console How to Post to DZone Article Submission Guidelines
View Profile
Sign Out
Refcards
Trend Reports
Events
Zones
Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
  1. DZone
  2. Software Design and Architecture
  3. Security
  4. AppSec Managers Should Have Empathy for Developers

AppSec Managers Should Have Empathy for Developers

AppSec is important, but it can be pretty rough on developers. In this article we take a look at why AppSec managers should have some empathy for those developers implementing a product or service.

Jim Jastrzebski user avatar by
Jim Jastrzebski
·
Feb. 14, 17 · Opinion
Like (0)
Save
Tweet
Share
2.36K Views

Join the DZone community and get the full member experience.

Join For Free
jjastrzebski's picture


developers don't always respond well to security assessments that highlight flaws in their code. with a little bit of empathy, it's not hard to understand why developers might react with frustration, annoyance, or even hostility.

security testing should be a dispassionate and routine part of the software development lifecycle – application security professionals will tell you it’s never personal. but developers invest time, attention, and emotional energy into the code they produce. pointing out errors in their code can make developers feel like their work is being picked apart, judged, and declared inadequate.

in my nearly 10 years with veracode, i've conducted thousands of consultation calls with developers to go over the results of a security assessment and help them take appropriate action to address security weaknesses. i've spoken with thousands of developers, and i've heard just about every kind of reaction developers can have to remediation.

i can tell you that virtually all developers i talk to care about application security . they care about the quality of the products they create, the integrity of the data their software handles, and the reputation of the organizations they work for.

software development can be very demanding, and developers do their best under difficult circumstances with occasionally poor resources. they might be dealing with design documents and functional requirements that neglect explicit security considerations, and aggressive timelines that make comprehensive testing a burden. often they lack the skillset for secure programming, which is not typically part of a developer's formal training .

in my experience, developers sometimes take security assessments very personally, and may internalize this implied criticism of their work as a criticism of their professionalism. programming is as much a creative process as it is a technical challenge, and developers understandably have pride of ownership over their code.

given the constant pressure on developers to meet deadlines or to accommodate changing requirements, it's understandable that when we give developers a security assessment and ask them to "fix it," it can feel like adding insult to injury.

as an appsec manager, you should understand the pressures on development teams and try to understand why they may appear resistant to security testing. in my next blog post, i'll describe the stages of grief a developer goes through after a security assessment, and explain how you can help developers accept security as just a part of the job, and not a personal affront to their abilities.

Software development Application security Empathy (software)

Published at DZone with permission of Jim Jastrzebski, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • Visual Network Mapping Your K8s Clusters To Assess Performance
  • How to Use MQTT in Java
  • 5 Factors When Selecting a Database
  • OpenID Connect Flows

Comments

Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends: