Our instructor-led PCI DSS Training Course aims to address a significant requirement of the updated PCI DSS 3.2.1, which is to ensure that relevant training is given to any software developers involved in developing and maintaining such financial applications and services.
If your web applications or systems have any involvement with processing or storing credit card data in any form, then the PCI DSS will almost certainly affect you. This still applies even if your web services / code is not financial by nature, but still resides on a shared resource which also stores or processes credit card data.
Security breaches and failures can lead to harsh penalties from member organisations (such as Visa and MasterCard), and the nature of the penalty depends on various factors such as the extent of non compliance with PCI data security standards found during a forensic investigation, and number of affected accounts / records breached.
The PCI Data Security Standards draw heavily on the current OWASP Top Ten Web Application Security Risks.
These largely affect cross-platform web technologies, and as such our course can be suitable for anyone involved in web development; our hands-on exercises and code demonstrations are delivered with examples in ASP.NET (with VB.NET or C#) or Java, but we can tailor the course for on-site delivery and focus on your development language / platform of choice (PHP, HTML5, Python et al).
This course isn’t just about ticking boxes and jumping through hoops – we aim to instil a good understanding of the importance of designing, developing and deploying secure web applications, and this course will be useful for any web developers who want to improve the robustness of their code. But if you have a particular need to top-up existing skills and don't need to cover the full syllabus, let us know and we can explore customisation options for you.
By the end of the course, you will have learnt about:
- Payment Card Industry Data Security Standards for Software Development
- Secure Development Lifecycle
- OWASP Top 10 Threats with code examples
- Crypto techniques
- Fuzz testing
Who should attend
Web Developers, Testers, Software Architects, Development Managers, Technical QA Managers
Prerequisites
Experience of data-driven web development in a language such as Java, C#, VB.NET, PHP. Knowledge of JavaScript would also be useful.
On-site PCI DSS Training
If you would like to discuss custom / on-site PCI DSS / Secure Web App Development training for any size of team, please get in touch – we would be glad to help build a course that meets your learning requirements.
We can take into account your existing technical skills, project requirements and timeframes, and specific topics of interest to tailor the most relevant and focussed course for you.
This can be particularly useful if you need to learn just the new features and Web App security Best Practices, or need to include extra topics to help with pre-requisite skills.
A number of clients have also asked for discussion about the security of SCADA and other Industrial Control Systems in relation to PCI DSS 3.2 which we’re more than happy to cover. Please let us know your requirements and we will do everything we can to accommodate them.
Full PCI DSS course syllabus
Introduction to Security
What is Application Security and why does it matter?
Payment Card Industry Data Security Standards - PCI-DSS
- Who / what is the PCI made up of?
- What PCI DSSmeans to Software Developers
- Ensuring compliance through design and coding Best Practises
SDL in depth
- Analysing security and privacy risk
- Attack surface analysis
- Threat Modeling
- Identifying the right tools
- Enforcing banned functions
- Static analysis
- Dynamic / Fuzz Testing
- Response Plan
- Final Security Review
Hands-on with the OWASP 2013 Top 10 Web Application Security Risks
- A1-Injection
- A2-Broken Authentication and Session Management
- A3-Cross-Site Scripting (XSS)
- A4-Insecure Direct Object References
- A5-Security Misconfiguration
- A6-Sensitive Data Exposure
- A7-Missing Function Level Access Control
- A8-Cross-Site Request Forgery (CSRF)
- A9-Using Components with Known Vulnerabilities
- A10-Unvalidated Redirects and Forwards
Beyond OWASP
- Data Protection Mechanisms (crypto and more)
- Fuzz testing and other tools
- Click jacking
- Response Splitting
- CWE/SANS Top 25 Most Dangerous Software Errors
- Exploiting authentication
- Language issues
- Data devaluation
- Tokenisation solutions
- Auditing and Logging Solutions
Summary
- Applying what you've learnt in the real world.
- Understanding the business impact of insecure software (beyond just PCI compliance)
