Audit and compliance teams are under pressure to comply with ever-changing regulations and internal audit requirements. Compliance is a key driver for implementing detective controls such as the CA Veracode service to mitigate risk from application-layer threats.
Combining rich reporting with automated compliance workflows, we’re able to simplify compliance processes and reduce the time and effort to prepare for audits.
We help lower the cost of compliance by automating common processes such as:
Compliance/audit reporting showing enterprise-wide compliance status across your global application infrastructure.
Compliance workflows to automate tasks such as notifications about policy changes and approval workflows for compensating controls.
Information sharing and collaboration across multiple teams that share responsibility for compliance including development, security, audit/compliance and network operations.
Validate critical systems are secure and compliant
Policy compliance: Use our cloud-based platform to independently verify compliance with internal policies and external regulations.
Evaluate any application against the PCI standard. The pre-configured report compares flaw results to the requirements in PCI-DSS sections 6.3.6, 6.5, and 6.6 and PA-DSS Sections 5.1.7 and 5.2.
Customizable reports for HIPAA, SOX, GLBA, NIST and MAS: Reports can easily be customized by starting with the pre-configured controls specified in the PCI policy and modifying the rules to support internal audit requirements specific to your organization.
Notification & approval workflows: Our built-in workflows reduce communication overhead as well as provide clearly documented approval processes to address internal audit requirements. For example, you can specify that:
Notifications about policy changes are sent automatically to the team assigned to the application; to any users with the Security Lead role; and to the application Business Owner. You can also send notifications about upcoming scans that are due, and when a flaw will go out of the grace period set in the policy.
Approvals must be obtained for items such as mitigating controls that temporarily remove the need to address the flaw via code-level remediation (e.g., changes to WAF rules, operating system features, network implementation or application design). You can also specify that approval is required for all new scan requests, such as requests from developers or third-party vendors to re-scan their applications; and for new users that self-register via SAML authentication.
Integration with GRC frameworks:Governance, Risk and Compliance (GRC) frameworks are often used to track strategic programs at the corporate level. We’ve integrated with the RSA Archer API via XML to share critical information such as application security scores; listings of all discovered flaws; and flaw status information (new, open, fixed, or re-opened). Summary data is also included for third-party assessments, including scores and top-risk categories. Similar integrations can be developed for other GRC systems, such as IBM OpenPages, through our APIs.
Simpler and more scalable
We're the most widely used cloud-based platform for securing web, mobile, legacy and third-party applications.
Fact is, more than 500 organizations trust our simpler and more scalable approach to secure their application infrastructures — including three of the top four banks in the Fortune 100. We’ve analyzed tens of thousands of applications for threats and we've been a Gartner Magic Quadrant Leader since 2010.
Using our smart, cloud-based and programmatic approach to application-layer security, you can drive your innovations to market faster — without hiring more consultants or installing more servers and tools — and without sacrificing security in the process.
Achieving Security and Compliance
Strategic organizations understand that compliance does not equate to security. By implementing best practices for security, organizations can demonstrate compliance while at the same time preventing:
- Data breaches of sensitive customer and financial data.
- Cyber-espionage of corporate intellectual property such as business plans, new product designs and proprietary algorithms and source code.
- Fraud due to unauthorized access by malicious insiders or outsiders.
- Brand impact due to website defacement by cyber-activists.
- Downtime due to outages in critical application components such as payment systems.