< Back to catalog

Web application security in Go

CYDGoWeb3d
3 days
On-site or online
Hands-on
Go
Developer
Instructor-led
Pricing Inquiry Download PDF
labs

24 Labs

case_study

10 Case Studies

Platform

Web

Audience

Go developers working on Web applications

Preparedness

General Go and Web development

Standards and references

OWASP, CWE and Fortify Taxonomy

Group size

12 participants

Outline

  • Cyber security basics
  • The OWASP Top Ten 2025
  • Wrap up

What you will learn

  • Getting familiar with essential cyber security concepts
  • Managing vulnerabilities in third party components
  • Understanding Web application security issues
  • Detailed analysis of the OWASP Top Ten elements
  • Putting Web application security in the context of Go
  • Going beyond the low hanging fruits
  • Understanding how cryptography supports security
  • Learning how to use cryptographic APIs correctly in Go
  • Input validation approaches and principles

Description

Your Web application written in Go works as intended, so you are done, right? But did you consider feeding in incorrect values? 16Gbs of data? A null? An apostrophe? Negative numbers, or specifically -1 or -2^31? Because that’s what the bad guys will do – and the list is far from complete.

Handling security needs a healthy level of paranoia, and this is what this course provides: a strong emotional engagement by lots of hands-on labs and stories from real life, all to substantially improve code hygiene. Mistakes, consequences, and best practices are our blood, sweat and tears.

The curriculum goes through the common Web application security issues following the OWASP Top Ten but goes far beyond it both in coverage and the details.

So that you are prepared for the forces of the dark side.

So that nothing unexpected happens.

Nothing.

Table of contents

  • Cyber security basics
  • The OWASP Top Ten 2025
    • A01 – Broken Access Control
      • Access control basics
      • Confused deputy
        • Insecure direct object reference (IDOR)
        • Path traversal
        • Lab – Insecure Direct Object Reference
        • Path traversal best practices
        • Authorization bypass through user-controlled keys
        • Case study – Remote takeover of Nexx garage doors and alarms
        • Lab – Horizontal authorization
      • File upload
        • Unrestricted file upload
        • Good practices
        • Lab – Unrestricted file upload
      • Server-side Request Forgery (SSRF)
        • Case study – SSRF and the Capital One breach
    • A02 – Security Misconfiguration
      • Configuration principles
      • Go configuration best practices
        • General Go security considerations
        • Go webapp security considerations
        • Limiting resource use in Go apps
        • Security headers
        • Package and dependency considerations
      • Web security configuration issues
        • Content Security Policy
        • Fetch directives
        • Source allowlisting
        • Strict CSP: using nonces and hashes
        • Navigation and reporting directives
        • Document restrictions and sandboxing
        • CSP best practices
      • Cookie security
        • Cookie attributes
      • Secrets management
        • Hard coded passwords
        • Best practices
      • XML entities
        • DTD and the entities
        • Entity expansion
        • External Entity Attack (XXE)
          • File inclusion with external entities
          • Server-Side Request Forgery with external entities
          • Case study – XXE vulnerability in Ivanti products
    • A03 – Software Supply Chain Failures
      • Using vulnerable components
      • Untrusted functionality import
      • Malicious Go packages
      • Supply chain security and the Software Bill of Materials (SBOM)
      • SBOM examples
      • Case study – The Polyfill.io supply chain attack
      • Vulnerability management
  • The OWASP Top Ten 2025
    • A04 – Cryptographic Failures
      • Cryptography for developers
        • Cryptography basics
        • Cryptography in Go
        • Elementary algorithms
          • Hashing
            • Hashing basics
            • Hashing in Go
            • Lab – Hashing in Go
          • Random number generation
            • Pseudo random number generators (PRNGs)
            • Cryptographically secure PRNGs
            • Weak PRNGs
            • Using random numbers
            • Lab – Using random numbers in Go
        • Confidentiality protection
          • Symmetric encryption
            • Block ciphers
            • Modes of operation
            • Modes of operation and IV – best practices
            • Symmetric encryption in Go
            • Handling IVs and block padding in Go
            • Lab – Symmetric encryption in Go
          • Asymmetric encryption
          • Combining symmetric and asymmetric algorithms
    • A05 – Injection
      • Input validation
        • Input validation principles
        • What to validate – the attack surface
        • Where to validate – defense in depth
        • When to validate – validation vs transformations
      • SQL injection
        • SQL injection basics
        • Lab – SQL injection
        • SQL injection best practices
          • Input validation
          • Parameterized queries
          • Lab – Using prepared statements
          • Case study – Hacking Fortnite accounts
      • Code injection
        • OS command injection
          • Lab – Command injection
          • OS command injection best practices
          • Avoiding command injection with the right APIs
          • Lab – Command injection best practices
          • Case study – Shellshock
          • Lab – Shellshock
          • Case study – Command injection in Gogs’ built-in SSH server
      • HTML injection – Cross-site scripting (XSS)
        • Cross-site scripting basics
        • Cross-site scripting types
          • Persistent cross-site scripting
          • Reflected cross-site scripting
          • Client-side (DOM-based) cross-site scripting
        • Lab – Stored XSS
        • Lab – Reflected XSS
        • XSS protection best practices
          • Protection principles – escaping
          • Lab – XSS fix / stored
          • Lab – XSS fix / reflected
          • XSS protection in React
  • The OWASP Top Ten 2025
    • A06 – Insecure Design
      • The STRIDE model of threats
      • Secure design principles of Saltzer and Schroeder
        • Economy of mechanism
        • Fail-safe defaults
        • Complete mediation
        • Open design
        • Separation of privilege
        • Least privilege
        • Least common mechanism
        • Psychological acceptability
      • Client-side security
        • Frame sandboxing
          • Cross-Frame Scripting (XFS) attacks
          • Lab – Clickjacking
          • Clickjacking beyond hijacking a click
          • Clickjacking protection best practices
          • Lab – Using CSP to prevent clickjacking
    • A07 – Authentication Failures
      • Authentication
        • Authentication basics
        • Multi-factor authentication (MFA)
        • Case study – The InfinityGauntlet attack
        • Time-based One Time Passwords (TOTP)
      • Session handling
        • Session management essentials
        • Why do we protect session IDs – Session hijacking
        • Session fixation
        • Session ID best practices
        • Session handling security considerations in single-page applications
      • Password management
        • Storing account passwords
        • Password in transit
        • Lab – Is just hashing passwords enough?
        • Dictionary attacks and brute forcing
        • Salting
        • Adaptive hash functions for password storage
        • Lab – Using adaptive hash functions in Go
      • Password policy
    • A08 – Software and Data Integrity Failures
      • Integrity protection
        • Message Authentication Code (MAC)
          • Calculating HMAC in Go
          • Lab – Calculating MAC in Go
        • Digital signature
          • Digital signature with RSA
          • Elliptic Curve Cryptography
            • ECC basics
            • Digital signature with ECC
          • Digital signature in Go
            • Lab – Digital signature with ECDSA in Go
      • Subresource integrity
        • Importing JavaScript
        • Lab – Importing JavaScript
        • Case study – The British Airways data breach
  • Wrap up
    • Secure coding principles
      • Principles of robust programming by Matt Bishop
    • And now what?
      • Software security sources and further reading
      • Go resources

Pricing

3 days Session Price

2250 EUR / person

  • Live, instructor led classroom training
  • Discussion and insight into the hacker’s mindset
  • Hands-on practice using case studies based on high-profile hacks and live lab exercises
Inquiry
Customized course

Tailor a course to your preferences

  • Send us a brief description of your business’s training needs
  • Include your contact information
  • One of our colleagues will be in touch to schedule a free consultation about training requirements
Inquiry

Inquiry

Interested in the trainings but still have some questions? Curious about how you can customize a training for your team? Send us a message and a team member will be in touch within 24 hours.

This field is required

This field is required

Send us your phone number if you prefer to discuss further on a call

This field is required

This field is required

This field is required

This field is required