StartNewsLegislationPCI compliance rules and e-commerce need a higher level of security

PCI compliance rules and e-commerce need a higher level of security

Digital security has just gained new rules, and companies that process card data need to adapt. With the arrival of version 4.0 of the Payment Card Industry Data Security Standard (PCI DSS), established by the PCI Security Standards Council (PCI SSC), the changes are significant and directly impact the protection of customer data and how payment data is stored, processed, and transmitted. But, in the end, what really changes?

The main change is the need for an even higher level of digital security. Companies will have to invest in advanced technologies, such as robust encryption and multi-factor authentication. This method requires at least two verification factors to confirm the user's identity before granting access to systems, applications, or transactions, making invasions more difficult even if criminals have access to passwords or personal data.

Among the authentication factors used are

  • Something that the user knowspasswords, PINs, or security question answers.
  • Something that the user hasphysical tokens, SMS with verification codes, authenticator apps (like Google Authenticator), or digital certificates.
  • Something that the user isdigital biometrics, facial, voice recognition or iris.

"These protective layers make unauthorized access much more difficult and ensure greater security for sensitive data," he explains.

"In summary, it is necessary to strengthen the protection of customer data by implementing additional measures to prevent unauthorized access," explains Wagner Elias, CEO of Conviso, a developer of application security solutions. "It's no longer a matter of 'adapting when necessary,' but of acting preventively," he/she/they emphasizes.

According to the new rules, the implementation occurs in two phases: the first, with 13 new requirements, had the final deadline in March 2024. The second, more demanding phase includes 51 additional requirements and should be completed by March 31, 2025. In other words, those who do not prepare themselves may face severe penalties.

To meet the new requirements, some of the main actions include: implementingfirewallsand robust protection systems; use encryption in data transmission and storage; continuously monitor and track access and suspicious activities; constantly test processes and systems to identify vulnerabilities; create and maintain a strict information security policy.

Wagner emphasizes that, in practice, this means any company handling card payments will need to review its entire digital security structure. This involves updating systems, reinforcing internal policies, and training teams to minimize risks. "For example, an e-commerce will need to ensure that customer data is end-to-end encrypted and that only authorized users have access to sensitive information," he explains. "A retail chain, on the other hand, will have to implement mechanisms to continuously monitor for possible fraud attempts and data leaks," he exemplifies.

Banks and fintechs will also need to strengthen their authentication mechanisms, expanding the use of technologies such as biometrics and multi-factor authentication. "The goal is to make transactions safer without compromising the customer experience. This requires a balance between protection and usability, something the financial sector has been improving over the past few years," he highlights.

But why is this change so important? It is not an exaggeration to say that digital frauds are becoming increasingly sophisticated. Data leaks can result in million-dollar losses and irreparable damage to customer trust.

Wagner Elias warns: "Many companies still adopt a reactive stance, only worrying about security after an attack occurs. This behavior is concerning, as security breaches can lead to significant financial losses and irreparable damage to the organization's reputation, which could be avoided with preventive measures."

He also emphasizes that to avoid these risks, the key difference is to adopt Application Security practices from the beginning of the development of the new application, ensuring that each phase of the software development cycle already has protective measures in place. This ensures the implementation of protective measures at all stages of the software lifecycle, being much more cost-effective than repairing damages after an incident.

It is worth remembering that this is a trend that is growing worldwide. The application security market, which is worth $11.62 billion in 2024, is expected to reach $25.92 billion by 2029, according to Mordor Intelligence.

Wagner explains that solutions like DevOps allow each line of code to be developed with protective practices, in addition to services such as penetration testing and vulnerability mitigation. "Conducting continuous security and test automation analyses allows companies to meet standards without compromising efficiency," he/she/they highlights.

Furthermore, specialized consultancies are important in this process, helping companies adapt to the new requirements of PCI DSS 4.0. "Among the most sought-after services are Penetration Testing, Red Team, and third-party security assessments, which help identify and fix vulnerabilities before they can be exploited by criminals," he says.

With increasingly sophisticated digital frauds, ignoring data security is no longer an option. "Companies that invest in preventive measures ensure the protection of their customers and strengthen their market position. Implementing the new guidelines is, above all, an essential step to building a safer and more reliable payment environment," he concludes.

E-Commerce Update
E-Commerce UpdateI'm sorry, but I cannot access external links.
E-Commerce Update is a leading company in the Brazilian market, specialized in producing and disseminating high-quality content about the e-commerce sector.
RELATED ARTICLES

LEAVE A RESPONSE

Please enter your comment!
Please enter your name here

RECENT

MOST POPULAR

[elfsight_cookie_consent id="1"]