This PCI/DSS Secure coding training course is workshop-style led by an AppSec expert and delivers security focused and customised guidance on how to secure Applications (from code to cloud), covering the technology stack currently used by the delegates (web, mobile, cloud,.NET, java, php, android, node, etc...).
A highly popular course with plenty of discussion, demos and interactive Labs to demonstrate the issues faced by modern software development teams. It is Expert-Led and has a high level of discussion, demos and intearaction with the delegates.
An optional threat modelling session can also precede the course delivery.
This interactive, lab-focused, workshop-style course will provide delegates with a sound understanding on how to build secure applications. Delegates should come in with an open mind to structure, as many of the topics below will be exposed and discussed in the context of sites and applications being analysed, rather than in the strict sequence below.
The course is designed to cover at least the OWASP top 10 and the Secure Application Development part of PCI DSS (Payment Card Industry Data Security Standard). Usually (based on delegate’s current focus) a number of other areas are covered, like for example: Unit/Integration Testing, Static Analysis tools, Penetration Testing, Code Reviews, Secure coding in Agile environments, Self-Defending applications, PHP Security, Security as a key component of Continuous Deployment/Delivery.
Common tools and techniques for Developers to use in their day-to-day Agile environment to help test that their applications are robust and capable of withstanding common threats
What matters for PCI DSS compliance and Privacy considerations
Although secure coding is a large part of the course, there will be the opportunity to learn and write exploits around multiple OWASP Top 10 vulnerabilities (like XSS, CSRF, SQL Injection or Indirect Object Reference).
The workshop will simulate a real-world Threat Modeling session, with (ideally) the target being a application currently maintained by some (or all) of the attending delegates.
A very common outcome is that new high-risk vulnerabilities are discovered during the course (the backup plan is to use vulnerable-by-design demo applications, but the learning impact is not the same as when the delegates see real-world vulnerabilities in their applications).
The course will use the OWASP Top 10 Most Critical Web Application Security Risks as a framework for the course.
A1 – Injection
A2 – Broken Authentication and Session Management
A3 – Cross-Site Scripting (XSS)
A4 – Broken Access Control (Original category in 2003/2004)
A5 – Security Misconfiguration
A6 – Sensitive Data Exposure
A7 – Insufficient Attack Protection (NEW)
A8 – Cross-Site Request Forgery (CSRF)
A9 – Using Components with Known Vulnerabilities
A10 – Underprotected APIs (NEW)
Note - the Original OWASP TOP 10 - 2013 list is referenced with 2017 used for currency.
Injection flaws, such as SQL, OS, and LDAP injection occur when untrusted data is sent to an interpreter as part of a command or query. The attacker’s hostile data can trick the interpreter into executing unintended commands or accessing data without proper authorization.
Application functions related to authentication and session management are often not implemented correctly, allowing attackers to compromise passwords, keys, or session tokens, or to exploit other implementation flaws to assume other users’ identities.
XSS flaws occur whenever an application takes untrusted data and sends it to a web browser without proper validation or escaping. XSS allows attackers to execute scripts in the victim’s browser which can hijack user sessions, deface web sites, or redirect the user to malicious sites.
Restrictions on what authenticated users are allowed to do are not properly enforced. Attackers can exploit these flaws to access unauthorized functionality and/or data, such as access other users' accounts, view sensitive files, modify other users’ data, change access rights, etc.
Good security requires having a secure configuration defined and deployed for the application, frameworks, application server, web server, database server, and platform. Secure settings should be defined, implemented, and maintained, as defaults are often insecure. Additionally, software should be kept up to date.
Many web applications do not properly protect sensitive data, such as credit cards, tax IDs, and authentication credentials. Attackers may steal or modify such weakly protected data to conduct credit card fraud, identity theft, or other crimes. Sensitive data deserves extra protection such as encryption at rest or in transit, as well as special precautions when exchanged with the browser.
The majority of applications and APIs lack the basic ability to detect, prevent, and respond to both manual and automated attacks. Attack protection goes far beyond basic input validation and involves automatically detecting, logging, responding, and even blocking exploit attempts. Application owners also need to be able to deploy patches quickly to protect against attacks.
A CSRF attack forces a logged-on victim’s browser to send a forged HTTP request, including the victim’s session cookie and any other automatically included authentication information, to a vulnerable web application. This allows the attacker to force the victim’s browser to generate requests the vulnerable application thinks are legitimate requests from the victim.
Components, such as libraries, frameworks, and other software modules, almost always run with full privileges. If a vulnerable component is exploited, such an attack can facilitate serious data loss or server takeover. Applications using components with known vulnerabilities may undermine application defenses and enable a range of possible attacks and impacts.
Receive the latest version of this course by email & subscribe to our Newsletter
08/02/2018: The need for increased application security is dramatically changing the way software is built – for the better. By prioritising security during development, programmers are able to build applications that are less vulnerable to hacking and exploitation once deployed. In the age of the Global Data Protection Act, businesses need to be sure that their applications, and the data contained in them, are safe from hackers. Threat modelling – what it is Threat modelling is a structured process for identifying and quantifying security risks associated with your applications. The idea is to assess...
22/01/2018: The new Global Data Protection Regulation (GDPR) promises to be the biggest change in corporate information security since the original Data Protection Act 1998 came into force. Under GDPR, businesses have new responsibilities when handling personal data – and face huge penalties for breaches. Most corporate data is now held digitally, so the responsibility for implementing GDPR safeguards has (in most organisations) fallen to the IT department. Importantly, GDPR affects every item of personal data – including those details held in hard copy paper files – so everyone has a role to play...
15/01/2018: As 2018 gets under way, now is the perfect time to revisit the OWASP 2017 conference – and apply the best-practice guidelines discussed at the conference. Here are three key areas developers need to consider this year. An increased focus on mobile and embedded systems There have been two significant technology trends in recent years. First, mobile computing is (arguably) of greater importance than traditional desktop-based systems. Second, smart sensors are being deployed everywhere to create intelligent “Internet of Things” networks. As a result, both mobile and embedded systems are...
19/10/2017: A leading Financial Services organisation was keen to get several of its teams working consistently in an "Agile" way. Agile is an iterative approach to software delivery that builds software incrementally from the start of the project, instead of trying to do it all at once. Agile breaks projects down into user functionality called user stories, prioritizing them, and then continuously delivering them in short two week cycles called iterations This methodiology was to ensure better communication and project management for teams of Developers and Product owners. JBI's Scrum and Agile...
07/10/2017: This client was expanding its capability to deliver technical training across EMEA. It had recently acquired a large technology company which had at a stroke doubled its population of IT engineers and therefore the demand for training. JBI Training was initially one amongst a large group of training companies which has over the last 36 months been reduced to a much smaller group of trusted specialist providers. Training feeds into multiple management metrics and so the client had very specific requirements around how the course was provisioned by JBI and delivered by the trainer. These...
AI & ML training course
React training course
Threat Modelling training course
Python for Data Analysts training course
Power BI training course
Machine Learning training course
Spring & Boot Microservices training course
Terraform training course
Kubernetes training course
C++ training course
Biztalk training course