ENCAPSULATION VULNERABILITIES

What Is an Encapsulation Vulnerability?

Encapsulation refers to a programming approach that revolves around data and functions contained, or encapsulated, within a set of operating instructions. Applications become vulnerable to an attack when they fail to separate or differentiate critical data or functionality within components. When an encapsulation vulnerability exists, bad code creeps across software components or "leaks" from an application. This problem can also lead to cross-domain attacks. Without strong and clearly defined boundaries between control spheres, attackers can gain unauthorized access to data and functions.

Encapsulation Is a Persistent Threat

Source: Veracode State of Software Security 2017

Anatomy of an Attack

Step 1: An attacker initiates a non-typical request to a web application or other exposure point and views the resulting error codes. These error codes provide clues about technologies, operating systems, product versions, and other system details.

Step 2: After obtaining detailed system or application information—including things like debugging information or logging data—the attacker fashions an assault based on known vulnerabilities. There are a variety of attack methods possible. These include trust boundary violations, protection mechanism failures, and deserialization of untrusted data.

Step 3: The attacker launches the attack to deny service, cause security mechanisms to fail, or crash a server. This breach can take place via a mobile platform, web server, or other computing system.

The Impact of an Attack

An encapsulation attack can lead to problems that range from relatively benign to catastrophic. By denying service, critical system functionality may be unavailable to users for a period of time. Switching off security controls may lead to extensive damage, including modified, destroyed or stolen data. There’s also the possibility of damage to applications and other tools and resources, or a ransomware attack.

SECURE CODING BEST PRACTICES HANDBOOK



Get the Handbook

Real-Life Attack Example

In 2016, the San Francisco Metropolitan Transit Agency’s Municipal Rail (known as MUNI) suffered a significant ransomware attack based on an encapsulation vulnerability. The perpetrator demanded a US $73,000 ransom from the transit authority. The transit agency had neglected to patch a Java deserialization flaw that had existed for more than a year. Fortunately, MUNI officials were able to quickly restore systems from backups and thus avoid paying the ransom.

Attack and Defense Code Examples

Example #1:

This example in C Language prints the path environment variable to the standard error stream:

Example #2:

This example in Java prints an exception code to the standard error stream:

The above example exposes a system to a breach by allowing an attacker to dump data into a console, write data to a log file, or view it as a remote user. The system may provide specific information about system vulnerabilities. It might also deliver general information or clues about the underlying operating system in use, the types or nature of applications, and the approach developers have taken in coding applications.

Example #3:

Here’s an example in C#

This example exploits a system or application using the same type of methodology as the Java example above.

Preventing Damage

The discovery of an encapsulation vulnerability requires an organization to cut access to the affected application, database, or system until it can be fully protected. In the case of ransomware, a backup allows the organization to return to a working state quickly and without paying the fee demanded by the attacker.

Remediation Is Critical

It’s critical to check all code for encapsulation vulnerabilities and protect all application sessions from information leakage. One of the most effective tools for this is static analysis. It’s also vitally important to understand how code functions and retest it in different environments and for different uses. For example, a code string may pose no risk in a single-user environment but may introduce a huge vulnerability in a multi-user framework. In a multithreading environment, it’s important to avoid storing user data in Servlet member fields and member fields to store information in the Servlet.

CA Veracode Can Aid in the Defense Against Encapsulation Vulnerabilities

CA Veracode Web Application Scanning can safely, accurately, and quickly discover web application flaws, including SQL injection, in running web applications, in either production or pre-production environments.

CA Veracode Static Analysis can accurately identify SQL injection vulnerabilities and other flaws in your application and its third-party components and tell your developers exactly where and how to repair them. All without ever looking at the source code.

Our cloud-based application security platform helps you manage your application security program, track progress, and educate your developers on avoiding and repairing SQL injection and other security flaws through integrated eLearning materials.

About CA Veracode Developer Training

Learn More

Common Web Application Vulnerabilities

Buffer Overflow

Cross-Site Scripting

Cross-Site Request Forgery

Directory Traversal

Failure to Restrict URL Access

Insecure Cryptographic Storage

Insufficient Transport Layer Protection

LDAP Injection

OS COMMAND INJECTION PRIMER: HOW THEY WORK AND HOW TO PREVENT ATTACKS

What is OS Command Injection?

Command injection refers to a class of critical application vulnerabilities involving dynamically generated content. Attackers execute arbitrary commands on a host operating system using a vulnerable application. They pass the bad data to the system shell through forms, cookies, and HTTP headers. This allows the attackers to gain control over a web site and carry out any action or process that the underlying application accommodates. Attackers who gain access to these systems can modify, manipulate, or read data; inject commands that steal data or attack infrastructure; and engage in other damaging activities. Command injection is highly dependent on privileges. It occurs when insufficient input validation takes place.

How Command Injection Works

Step 1: Attackers identify a critical vulnerability in an application. This allows them to insert malicious code into the OS and gain any functionality the underlying application offers. The attackers can unleash the attack even without direct access to the OS.

Step 2: The attacker alters dynamically generated content on a web page using HTML code through an input mechanism such as a form field or cookies.

Step 3: Once the code is inserted into the affected web page, browsers interpret the code. This allows the attackers to execute specific commands across user's computers — along with both users’ networks and the infected system's network.

SECURE CODING BEST PRACTICES HANDBOOK



Get the Handbook

Anatomy of an Attack

There are two basic ways attackers deploy OS command injection:

An application executes a fixed program that operates under its control. After the breach, it accepts outside input as arguments. These arguments trigger various actions and behavior.

Example: The attack script accesses the system call ("nslookup [hostname]") to run nslookup with the HOSTNAME appearing as an argument from the user. If the program does not removed separators included with the externally generated HOSTNAME argument, the attacker can place separators inside the argument and executive his or her own commands.

An application relies on input to select the program that will run along with the commands to include in the attack. The application sanitizes the input and then redirects the command to the OS.

Example: The application relies on exec([COMMAND]). The input is supplied from an external source. Once an attacker controls the [COMMAND] argument, he or she can execute arbitrary commands and desired scripts on the system.

The Impact of an Attack

Problems resulting from an OS command injection attack can range from minor to highly disruptive. An attacker might alter or corrupt a database, steal customer records, use an API to launch a specific process or event, or launch a distributed denial of service (DDoS) attack. Once attackers have gained control of a server, they can use the underlying application to exploit any and all capabilities built into the software. The resulting damage is determined by the user authorizations and security protections an organization has in place. What's more, attackers may retain access to systems even after an organization has detected and fixed the underlying vulnerability.

Preventing Damage

After discovering that an OS command injection attack has taken place, it's critical to cut off access to the application that’s been compromised. This may require a temporary solution, such as blocking access to the vulnerable script until a development or security team can resolve the underlying issue. The task can be addressed in one of two ways: making changes using the native functionality of the web server or altering system access permissions to the affected file.

Remediation is Critical

It's vital to address potential vulnerabilities that could lead to an OS command injection attack. There are a few ways to handle the task:

Preventing manipulation at the source. It's vital that any applications accessible through a web browser avoid user-controllable data in operating system commands. Development and cybersecurity teams should focus on the use of code that doesn't allow for manipulation of server-level tasks via unintended commands.

Rejecting unacceptable code. If it's impossible to find a safer and more secure way to perform server-level tasks, then it's critical to strictly validate all user data. This is often achieved by creating a whitelist of acceptable values. In addition, some organizations limit input to short alphanumeric strings. Any input outside the range of acceptable data is automatically rejected by the system.

Controls over APIs. In some cases, an application might pass a command string for an API to a shell interpreter that handles command chaining and redirection. This can lead to a breach. Instead, the application should only launch a specific process based on a specific name and command line parameters. This way, even if attackers circumvent basic input validation methods, their options and choices are limited.

CA Veracode Can Help with OS Command Injection

CA Veracode Web Application Scanning can safely, accurately, and quickly discover web application flaws, including OS command injection, in running web applications in either production or pre-production environments.

CA Veracode Static Analysis can accurately identify OS command injection vulnerabilities and other flaws in your application and its third-party components, and tell your developers exactly where and how to repair them, all without ever looking at the source code.

Our cloud-based application security platform helps you manage your application security program, track progress, and educate your developers on avoiding and repairing OS command injection and other security flaws through integrated eLearning materials.

About CA Veracode Developer Training

Learn More

Common Web Application Vulnerabilities

CRYPTOGRAPHIC

The danger of Insecure Cryptographic Storage.

Insecure Cryptographic Storageis a common collection of vulnerabilities related to storing sensitive data without the appropriate encryption.

Ideally, in a secure software development lifecycle, all sensitive data should be encrypted. This would include making sure the right data is encrypted, that keys are properly stored and managed, that algorithms known to be bad are not used as part of the process, and that developers are not implementing their own cryptographically insecure technology.

When these guidelines are not followed, and Insecure Cryptographic Storage flaws exist, attackers may gain unauthorized access through malicious software to steal sensitive information like trade secrets, personal information, edit card numbers, personally identifiable information (PII) and trade secrets may be exposed.

To address Insecure Cryptographic Storage issues, developers should also:

  • Identify all sensitive information and encrypt it, even when it’s stored on a hard drive.
  • Overwrite sensitive memory locations as soon as the data is no longer needed in memory.
  • Make sure that sensitive data cannot be overwritten.
  • Identify users who should and should not have access to sensitive data.
  • Identify sensitive data read into memory and overwrite it with random data using strong encryption.

Preventing Insecure Cryptographic Storage with CA Veracode.

There are essentially two approaches to finding and remediating Insecure Cryptographic Storage issues. When the wrong data is being encrypted or keys are being improperly managed, IT teams must reevaluate the scope of their applications, assess internal business processes and find ways to ensure that best practices are being followed.

When Insecure Cryptographic Storage issues arise from using insecure algorithms or deploying an organization’s own insecure cryptography, application security testing technology can remediate a wide range of issues. That’s where CA Veracode can help.

CA Veracode is a leading provider of cloud-based application security testing services that enable organizations to protect their most important software. Built on a unified cloud platform, our suite of testing technologies can be used throughout the SDLC from inception through production toquickly, easily and cost-efficiently find and fix flaws like SQL injection, broken authentication and session management, cross site scripting and more. Our testing services take security beyond software firewalls, adding powerful application-layer security to network security tools.

Software testing services for Insecure Cryptographic Storage.

CA Veracode application security testing services for remediating Insecure Cryptographic Storage include:

  • CA Veracode Greenlight, a service that runs in a developer’s IDE to provide immediate feedback on potential flaws as code is being built.
  • CA Veracode Static Analysis, a service that scans binaries to identify weaknesses and vulnerabilities in code that is built, bought and assembled.
  • CA Veracode Software Composition Analysis, for inventorying and managing vulnerabilities in open source and commercial code.
  • CA Veracode Web Application Scanning, a service that discovers, scans and monitors websites and applications.
  • CA Veracode Vendor Application Security Testing, a service that can find flaws like Insecure Cryptographic Storage in third-party software without requiring access to source code.

Learn more about Insecure Cryptographic Storage and CA Veracode, or visit our AppSec knowledgebase to get answers to questions like “What is spoofing?

UNIT TESTING TOOLS

Unit testing tools can streamline application security.

Unit testing is an approach to application security that uses unit testing tools to determine whether small individual microservices and units of source code are free of flaws and fit for use. By scanning smaller bits of code earlier in the process, unit testing tools enable developers to find flaws faster, fix them more easily and deliver more secure applications with less cost.

The challenge of unit testing tools is the amount of time they can take to administer. Some developers find that writing unit tests can take as long as actually writing the code to be tested. For software development teams facing aggressive build timelines, the added delays that unit testing tools introduce are simply acceptable.

That’s where CA Veracode can help. By providing automated unit testing tools that enable developers to test code quickly, easily and continually, CA Veracode helps software teams build more secure applications from the very start of development.

Unit testing tools from CA Veracode.

As a leading provider of automated software testing solutions, CA Veracode helps to secure and protect the software the world relies on for business-critical operations. CA Veracode’s application security solutions are built on a unified platform that combines automation, process and speed to deliver comprehensive testing technology. In addition to unit testing tools, CA Veracode provides solutions for static analysis, blackbox testing techniques, software composition analysis, vendor application security testing and other approaches to evaluating code. With CA Veracode, developers have the tools they need to find flaws at the very point in development/deployment chain where it is easiest and most cost efficient to fix them.

CA Veracode Greenlight provides unit testing tools that can find security defects in code as it is being written and provide contextual remediation suggestions to fix issues within seconds – right in the developer’s IDE. Most CA Veracode Greenlight scans complete in less than 10 seconds, enabling developers to continue building applications without delay. Greenlight runs in the background and provides actionable and accurate results with very few false positives. With CA Veracode, developers get immediate feedback as soon as a flaw is introduced, and positive feedback when they have taken action to secure the application.

Advantages of CA Veracode’s unit testing tools.

With unit testing tools in CA Veracode Greenlight, development teams can:

  • Identify and remediate flaws in software earlier in the process – with less effort to find them and less time to fix them.
  • Flag flaws as soon as they are written, providing developers with recommendations for efficient remediation.
  • Protect applications with CA Veracode’s static analysis engine which has scanned more than 2 trillion lines of code to date.

 

Learn more about unit testing tools and CA Veracode, and about CA Veracode solutions for mitigating shellshock and complying pci 3.0 with shellshock

UNIT TESTING

The challenge of unit testing.

Unit testing is a software testing method that has been gaining in use and popularity in recent years. By testing small individual units of source code as applications are developed – rather than waiting until a later security hardening stage – defects can be found earlier in the process and flaws can often be remediated faster and with less cost. Unit testing supports Agile development, as it builds testing into the process in a way that let developers make changes more easily. Ultimately, unit testing improves the quality of code and of the shipped product.

The challenge of unit testing: time. Writing effective unit testing programs can sometimes take longer than writing the code to be tested. And for many software development teams, this additional hurdle adds unacceptable delays to the build schedule.

That’s where CA Veracode can help. By providing automated software testing tools that streamline testing processes, CA Veracode is helping to make unit testing faster and easier, enabling teams to use unit testing tools to increase the pace of development rather than slow it.

Unit testing solutions from CA Veracode.

CA Veracode provides application security solutions and Dev Ops tools that help enterprises protect the software they rely on for business-critical operations. Built on a unified platform, CA Veracode testing solutions and software development tools provide a variety of testing methods – from unit testing and static analysis to black box testing techniques and software composition analysis – delivering a comprehensive approach that makes application security testing easier, more effective and more-cost efficient.

CA Veracode Greenlight is a unit testing solution that runs in the background of an IDE and scans smaller units of code as they are being written. Results are immediate, accurate and actionable, with very low false positives. Greenlight provides feedback as soon as a flaw is introduced, along with contextual remediation advice to help fix the issue quickly. Developers can rescan in seconds to ensure that the defect no longer exists. And Greenlight even provides positive feedback when developers take active steps to secure an application.

Benefits of CA Veracode’s unit testing tools.

With unit testing technology from CA Veracode, organizations can

  • Test units of code earlier in the development process to find and fix flaws when it is most cost-effective to remediate them.
  • Combine unit testing with static analysis to ensure that applications meet the organization’s security requirements.
  • Enable developers to get immediate feedback as they are in the act of writing code.
  • Benefit from CA Veracode’s proven application testing engine which has analyzed over 2 trillion lines of code.

 

Learn more about unit testing and CA Veracode, and about CA Veracode’s solutions for PCI 3 compliance.

SOFTWARE DEVELOPMENT TOOLS

Increase speed and security with automated software development tools.

As organizations work to protect software applications from an ever-evolving landscape of threats, automated software development tools for testing can help to improve security while enabling development teams to meet aggressive deadlines.

In a world that is increasingly dependent on mission-critical applications, secure software development is a high priority for enterprises everywhere. Yet, in a recent survey, fewer than 10% of enterprise security officers were certain that their most important applications were tested for flaws before and during production.

In too many cases, build deadlines deter the kind of comprehensive security testing that can find and fix flaws during development. That’s often because traditional software development tools for security testing are cumbersome and time-consuming to use. The result: software is either tested for flaws late in the development process, or worse – not tested at all.

CA Veracode’s automated software testing provide an easy solution to this pervasive problem. With comprehensive software development tools for testing applications from inception through production, CA Veracode enables organizations to produce better software faster and more cost-efficiently.

Software development tools for testing from CA Veracode.

CA Veracode software development tools and application security solutions protect the software that enterprises rely on every day. With CA Veracode, development teams can buy, build and assemble applications with greater confidence that they are free from vulnerabilities and flaws.

CA Veracode’s software development tools are built on a unified platform that combines automation, speed and process to add security testing throughout the SDLC. With CA Veracode’s SaaS-based software development tools, organizations can test software at any point in the development process where it is easy and cost-efficient to do so.

CA Veracode’s comprehensive software development tools.

CA Veracode provides a suite of software development tools that provide multiple approaches to finding and remediating flaws.

CA Veracode Vendor Application Security Testing provides software development tools that can assess the security of third-party applications without needing access to source code.

  • Static Analysis tools scan software from the inside out, reviewing compiled binaries for common vulnerabilities such as cross-site scripting and SQL injection.
  • CA Veracode Greenlight provides developers with immediate feedback on potential flaws as code is being written, running in the background of the developer’s preferred IDE. Greenlight also enables unit testing on microservices as they are being developed.
  • CA Veracode Web Application Scanning (WAS) discovers and inventories all external websites and applications, running lightweight scans on thousands of sites in parallel to identify and prioritize flaws for remediation. WAS combines static analysis and blackbox testing techniques for a comprehensive approach to security testing.
  • CA Veracode Software Composition Analysis offers tools for identifying flaws in open source and commercial applications.

 

Learn more about software development tools from CA Veracode, and about CA Veracode’s solutions for PCI 3 compliance and PCI security.

SHELLSHOCK

The danger of Shellshock to application security.

Shellshock is an application-layer vulnerability in Bash, a widely-used UNIX/Linux program. Shellshock has a severity ranking of 10 – the highest level – on the NVD Common Vulnerability Scoring System Support (CVSS) because of how easy it is to execute and how severely it can damage an organization. Attackers use Shellshock to expose sensitive files, access databases and install malware that can turn a system into a component of a DDoS botnet. The applications that are most vulnerable to a Shellshock attack are public-facing web applications, especially legacy applications that rely on the Bash program.

While Shellshock is fairly easy to remediate in an individual program, most enterprises have thousands of public-facing web applications, including many legacy applications they may not even be aware of. Using traditional testing tools on thousands of applications at once can be highly expensive and time-consuming, but CA Veracode provides an innovative solution that can help.

Testing for Shellshock with CA Veracode.

CA Veracode is a leading provider of automated software testing tools that help protect the software the world depends on.

CA Veracode’s comprehensive suite of SaaS-based application security solutions include software development tools for testing applications from inception through production, including unit testing tools, static analysis tools, blackbox testing techniques, software composition analysis and more. By employing CA Veracode’s dev ops tools throughout the SDLC, development teams can find and fix vulnerabilities in software at the point when it is easiest and most cost efficient to do so.

How CA Veracode helps to protect against Shellshock.

CA Veracode Web Application Scanning (WAS) provides a highly effective solution for combating Shellshock. Built on a massively parallel, auto-scaling cloud infrastructure, WAS performs scans on thousands of websites and applications in parallel to identify flaws and provide guidance for remediation.

To find Shellshock vulnerabilities, WAIS discovers all the public-facing web applications of an organization, even those that IT has lost track of and applications outside the normal corporate IP range. These may include sites acquired through M&A or temporary sites hosted with cloud service providers. Once these applications and websites have been inventoried, CA Veracode WAS automatically crawls all pages on a site and probes the surface of web applications to find flaws like the Shellshock vulnerability. This approach to vulnerability scanning is far more thorough and exhaustive than traditional methods which only inject signatures into a few well-known directories.

 

Learn more about Shellshock and CA Veracode solutions for PCI security.

PCI SECURITY

CA Veracode testing tools enable PCI security compliance.

For software development organizations, complying with Payment Card Industry Data Security Standard 3.0 (PCI 3.0) requires an investment in application testing for PCI security.

PCI 3 directs software organizations to comply with secure guidelines for developing applications and requires that custom application code can be adequately scanned for potential vulnerabilities. To meet these PCI security dictates, organizations need a consistent approach to application security and powerful software development tools for application testing.

Because PCI security requirements apply both to software in development and software in production, enterprises may need solutions to test thousands or tens of thousands of public-facing web applications that are already running. They’ll also need Dev Ops tools that can integrate testing throughout the development process, from inception through preproduction. And tools to quickly scan and evaluate third-party code are a must.

CA Veracode enables organizations to easily comply with PCI security requirements by providing a comprehensive suite of solutions that make testing easier, faster and less costly.

PCI security solutions from CA Veracode.

CA Veracode solutions help to seamlessly integrate security and testing into development processes to ensure that secure code is synonymous with quality code. By combining automation, process and speed, CA Veracode technology enables organizations to eliminate software flaws at the most cost-efficient point in the development/deployment chain.

To promote PCI security, CA Veracode enables developers to automatically test applications and receive results, often within four hours. Rather than relying on on-premise hardware and software, developers can use CA Veracode’s cloud-based services to test applications without needing to open a new environment. CA Veracode’s suite of solutions provides a comprehensive approach to testing, with tools for static analysis, black box testing techniques, software composition analysis, vendor application security testing and more.

How CA Veracode simplifies PCI security.

  • To comply with PCI security mandates, IT administrators can use CA Veracode’s predefined policies to authorize automated scans for a variety of applications. Once configured, the CA Veracode platform can:
  • Automatically test software in development, pre-production and production.
  • Provide analysis of the results, prioritized by severity, along with detailed remediation instructions that enable developers to re-create and fix flaws faster.
  • Retest software as needed to demonstrate successful remediation and to document progress against planned timelines.
  • Provide detail of compliance with PCI security guidelines, including proof that applications have been tested and that remediation has been accomplished.

 

Learn more about PCI security and CA Veracode, and about CA Veracode solutions for mitigating Shellshock vulnerabilities.

PCI 31

Improve PCI 3 compliance with help from CA Veracode.

For software organizations, complying with Payment Card Industry Data Security Standard 3.0 (PCI 3) can be a significant burden.

PCI 3 mandates that organizations meet strict guidelines for security when developing applications, and that third-party custom code can be scanned for vulnerabilities. Compliance with PCI 3.0 requires organizations to have a robust testing program in place, with tools for evaluating third-party software.

But managing PCI security can be costly and time-consuming, adding unacceptable delays to timelines for developing new applications. And organizations that have thousands of web applications – some which they may not even know about – faced serious hurdles to ensuring that every piece of software has been adequately scanned for vulnerabilities.

As a leading provider of application security testing solutions, CA Veracode can help with PCI 3 compliance by providing dev ops tools that integrate testing throughout the SDLC and provide an easy way to evaluate third-party code.

PCI 3 security solutions from CA Veracode.

CA Veracode application security solutions help organizations protect business-critical software. Built on a unified platform, CA Veracode’s comprehensive testing tools include static analysis,unit testing, software composition analysis, black box testing techniques, vendor application security testing and other technologies for scanning code as it is built, purchased and assembled to rid it of flaws and vulnerabilities.

With CA Veracode’s automated testing solutions, software development teams can ensure PCI 3 compliance by testing for flaws at multiple points in the software development lifecycle. From scanning code as it is being written to analyzing binaries of applications already in production, CA Veracode delivers the solutions that make application security easier, faster and less costly

How CA Veracode makes it easier to comply with PCI 3 requirements.

To ensure compliance with PCI 3 guidelines, IT administrators can assign predefined policy for CA Veracode solutions to each application and authorize automated scans. Once this is done, the CA Veracode platform will:

  • Perform automatic tests of designated applications in development and in production.
  • Analyze the results, provide detailed findings and categorize issues based on severity.
  • Deliver remediation recommendations that enable developers to fix vulnerabilities more quickly.
  • Retest software and provide data on the effectiveness of remediation as well as progress against target timelines.
  • Provide proof of compliance with PCI 3, including documentation that applications have been tested and that remediation has been accomplished.

 

Learn more about PCI 3 and CA Veracode, and about CA Veracode’s solutions for mitigating Shellshock vulnerabilities.

PCI 3.0

Automated testing solutions help ensure PCI 3.0 compliance.

The Payment Card Industry Data Security Standard 3.0 (PCI 3.0) establishes data and network security standards intended to protect the financial data and personal information of millions of credit card users. For software development organizations, compliance with PCI 3.0 is critical to avoid penalties and fines, not to mention the irreparable damage to business and reputation that a critical software flaw can cause.

For development teams, the most important requirements of PCI 3 have to do with adhering to secure guidelines when developing applications and ensuring that custom code is scanned for potential flaws. Complying with PCI 3.0 requires well-designed security testing protocols that can consistently look for vulnerabilities in software throughout development and in production. Development teams also need ways to successfully scan third-party and open source components for security flaws.

For organizations that have thousands or tens of thousands of applications in production, ensuring PCI 3.0 compliance can be remarkably expensive, and the time required to test software at a variety of stages can jeopardize the ability to meet build deadlines.

That’s where CA Veracode can help. With a suite of automated testing solutions and dev ops tools, CA Veracode enables organizations to comply more easily with PCI 3.0 by embedding testing throughout the SDLC, from inception through production, and by providing organizations with an easy way of evaluating third-party software.

Solutions for PCI 3.0 security from CA Veracode

CA Veracode’s application security testing solutions and services help enterprises protect the software they rely on to innovate and compete. CA Veracode’s comprehensive technologies provide multiple approaches to PCI security testing, including static analysis, blackbox testing techniques, penetration testing, unit testing, software composition analysis and vendor application security testing. When using CA Veracode’s automated testing tools, software development teams can more easily find and fix flaws at the easiest and most cost-efficient point in the development chain.

How CA Veracode supports PCI 3.0 requirements.

With CA Veracode, development teams can improve compliance of PCI 3.0 by automatically and consistently testing for vulnerabilities. Administrators can assign predefined policy for PCI compliance to each application, authorizing automated application scans at critical junctures during the SDLC. CA Veracode’s technology will:

  • Automatically test applications and provide analysis of the results.
  • Prioritize issues by severity and deliver recommendations and instructions that accelerate remediation.
  • Retest software as needed to demonstrate successful fixes.
  • Demonstrate compliance with PCI 3.0 by providing documentation that applications have been tested and fixed.

 

Learn more about PCI 3.0 and CA Veracode, and about solutions for mitigating the Shellshock vulnerability.

Pages

 

 

contact menu