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 Video Library
Refcards
Trend Reports

Events

View Events Video Library

Related

  • Why Developers Should Pay Attention to Internal Directory Security
  • Bridging the Gap: How Developers and Security Professionals Can Collaborate for Better Cybersecurity
  • Navigating BNPL Integration: Key Steps and Best Practices for Developers
  • Less Time Learning, More Time Building

Trending

  • Detecting Bugs and Vulnerabilities in Java With SonarQube
  • LLM Integration in Enterprise Applications: A Practical Guide
  • What Nobody Tells You About Multimodal Data Pipelines for AI Training
  • The Invisible OOMKill: Why Your Java Pod Keeps Restarting in Kubernetes
  1. DZone
  2. Software Design and Architecture
  3. Security
  4. With the Right Support, Developers Can Lead Your Organization to Superior PCI-DSS 4.0 Compliance

With the Right Support, Developers Can Lead Your Organization to Superior PCI-DSS 4.0 Compliance

The Payment Card Industry Data Security Standard (PCI-DSS) version 4.0 will be transformative for most businesses, requiring upgrades to security processes.

By 
Matias Madou user avatar
Matias Madou
·
Dec. 20, 23 · Opinion
Likes (1)
Comment
Save
Tweet
Share
2.6K Views

Join the DZone community and get the full member experience.

Join For Free

The Payment Card Industry Data Security Standard (PCI-DSS) version 4.0 will change almost everything about security for any business or organization that accepts electronic payments, which is a vast majority of them. And make no mistake, this update will be transformative for most businesses, requiring them to upgrade many of their security processes and potentially roll out new protections regarding encryption, authentication, access control, key management, and other areas that they may have been slow to embrace before now.

Due to the complexity of the new requirements, organizations have been given until March 2025 to become fully compliant. But that deadline will arrive sooner than most people realize. In fact, many forward-thinking companies are taking steps right now to enable their developers to navigate the pending compliance landscape. 

Going Beyond Check-the-Box Training

An organization’s developers write the code that much of their infrastructure relies on, so it makes sense that they are a good place to start when it comes to implementing the new PCI-DSS 4.0 requirements. However, most developers will need strategic support to upskill as part of an updated security awareness program. This is to ensure that they have the experience needed to implement and maintain the higher levels of security required by the new standard. 

In fact, requirement 12.6.2 of PCI-DSS 4.0 directs organizations to implement a formal security program, and to keep it updated with the latest threat information and defensive techniques. With the older standard, basic security programs or even “check-the-box”-style annual compliance training met the objective. This new standard mandates so much more, even requiring that security training programs address specific threats and vulnerabilities within a company’s environment. For example, if stolen identities are a big problem for an organization, then the training needs to address that.

It's clear that minimal training will no longer be adequate from either a practical standpoint or for complying with the new standard. Instead, organizations need to provide developers with comprehensive, agile learning pathways that teach them how to apply security best practices to their real, everyday work. By going beyond minimum compliance efforts and providing developers with the resources they need to truly understand security, organizations can empower their developers to make better security decisions overall while also complying with PCI-DSS 4.0.

The good news is that many of the new requirements in PCI-DSS 4.0 are targeted toward areas that most developers are already familiar with like authentication, encryption, access control, key management, and others. When developers are given right-fit, relevant and familiar resources to grow their skills, organizations can more easily prepare them for the new standards and increased responsibilities that PCI-DSS 4.0 will require.

Using PCI-DSS 4.0 as a Runway to Better Security Overall

While addressing developer needs with good security education will be key to successfully complying with the new PCI-DSS 4.0 standard, the effort of moving an organization towards better cybersecurity does not need to end there. Yes, the requirements are rigorous, but since most organizations will need to work to comply with them, there is no reason not to use that effort as a springboard for launching better security awareness and training overall. This will not only help an organization meet compliance requirements, but also start to foster a culture of positive security that prioritizes best practices and ensures that everyone in the organization is working towards the same, security-first goal. 

The security upgrades mandated by PCI-DSS 4.0 provide a perfect excuse for companies to invest in improved security best practices and training, and to embrace a better overall security culture within their organization.
Developers can more easily achieve higher levels of security maturity if their companies invest in a program that lets them integrate their skills in secure coding with relevant tools and training. This can, in turn, help to create a culture of security where developers are further empowered to make better decisions that improve their organization’s overall security posture well beyond even the rigorous new PCI-DSS 4.0 standards.

Payment card industry dev security

Opinions expressed by DZone contributors are their own.

Related

  • Why Developers Should Pay Attention to Internal Directory Security
  • Bridging the Gap: How Developers and Security Professionals Can Collaborate for Better Cybersecurity
  • Navigating BNPL Integration: Key Steps and Best Practices for Developers
  • Less Time Learning, More Time Building

Partner Resources

×

Comments

The likes didn't load as expected. Please refresh the page and try again.

  • RSS
  • X
  • Facebook

ABOUT US

  • About DZone
  • Support and feedback
  • Community research

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

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

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 3343 Perimeter Hill Drive
  • Suite 215
  • Nashville, TN 37211
  • [email protected]

Let's be friends:

  • RSS
  • X
  • Facebook