Information Technology and Communications

Building Security Testing Strategies for Sensitive Applications

Practical training in application security testing, grounded in real cases and applied to your own operation.

  • 5training days
  • 4modules
  • 8sessions
  • 32topics
View packages and pricesCourse outline
Building Security Testing Strategies for Sensitive Applications
5days

About the programme

Course Overview

Systems supporting application security testing fail in ways that are obvious afterwards and invisible before. Security and delivery speed are traded against each other in this strand of technology and systems delivery whether or not anyone says so. Participants develop a defensible line of reasoning for the choices they make about the technology and systems delivery capability. Practitioner evidence points the same way: application security testing improves fastest where responsibility for it is named and owned. Moving the technology and systems delivery discipline from written policy into daily practice is not achieved by a single decision. The course covers the wider technology and systems delivery agenda at the level of detail needed to act, and stops there. The material serves both public bodies and commercial organisations dealing with application security testing. Discussion is anchored to worked examples of this strand of technology and systems delivery rather than to abstract argument. The programme ends where implementation begins, with the technology and systems delivery discipline broken into steps someone can start on Monday.

Expected Learning Outcomes

  • Structure the service desk and support model for application security testing.

  • Define the availability, performance and recovery targets for application security testing.

  • Design a training and briefing approach that sustains competence in application security testing.

  • Design the architecture of application security testing around its failure modes, not only its happy path.

  • Set the minimum documentation for application security testing that is genuinely necessary, and stop there.

  • Test the organisation's response to application security testing under conditions that are less than ideal.

  • Control technical debt in application security testing deliberately rather than by neglect.

Who Should Attend

  • Quality and test engineers verifying application security testing.

  • Information security specialists protecting application security testing.

  • Staff seconded into improvement work on application security testing.

  • Specialists advising senior management on application security testing.

  • Solution architects designing application security testing.

  • Infrastructure and platform engineers operating application security testing.

Course Modules

Open any module to see its sessions and topics.

01

Application security testing: capacity, performance and load

2 sessions · 8 points

Session 1Sizing capacity for application security testing on measured growth

  • Configure alerting on application security testing that reflects what users experience.
  • Define the trigger that would require application security testing to be redesigned.
  • Record the technical debt in application security testing and schedule repayment.
  • Build the competence framework that supports application security testing.

Session 2Dependencies and supply chain risk in application security testing

  • Document the runbook for application security testing to the level a new engineer could use.
  • Prepare the summary of application security testing that senior management will read.
  • Test the procedure for application security testing against a realistic scenario.
  • Review access rights on application security testing and remove what is no longer needed.
02

Application security testing: change control and rollback

2 sessions · 8 points

Session 1Monitoring application security testing from the user's point of view

  • Establish what evidence demonstrates application security testing is under control.
  • Identify single points of dependency in application security testing and reduce them.
  • Set the review interval for application security testing and who attends.
  • Confirm that reporting on application security testing reaches the people who can act.

Session 2Running an incident on application security testing calmly

  • State the availability and recovery objectives for application security testing as numbers.
  • Run a load test on application security testing at expected peak plus a margin.
  • Apply change control to application security testing including emergency changes.
  • Set escalation thresholds for application security testing that work out of hours.
03

Application security testing: build, pipeline and release discipline

2 sessions · 8 points

Session 1Proving the backup of application security testing by restoring it

  • Identify the single points of failure in application security testing.
  • Confirm the support model and escalation path for application security testing.
  • Inventory third-party dependencies inside application security testing and their update status.
  • Name a single owner for each element of application security testing.

Session 2Escalation and decision rights in application security testing

  • Establish the boundary of application security testing and record what sits outside it.
  • Identify the data already collected that bears on application security testing.
  • Restore a backup of application security testing in a test environment and time it.
  • Prepare the response for the most likely failure in application security testing.
04

Application security testing: security, identity and least privilege

2 sessions · 8 points

Session 1Who answers for application security testing, and to whom

  • Assess the exit route from any cloud or vendor dependency in application security testing.
  • Decide what will be stopped to create capacity for application security testing.
  • Review logging on application security testing for coverage and retention.
  • Define incident severity levels for application security testing and the response each triggers.

Session 2Building lasting competence in application security testing

  • Write down the assumptions underpinning the approach to application security testing.
  • Measure current load on application security testing and project it forward twelve months.
  • Confirm every release of application security testing can be rolled back within a defined time.
  • Record the rationale for each significant choice made about application security testing.

Choose the package that suits you

Silver Package

At least 3 people

USD1,250
  • Workshop or Program Participation
  • Airport Transfers
  • Customized Badge
  • Expert Mentorship (Private Sessions)
  • Supervision & Secretarial Services
  • Accredited Certificate of Participation
  • Complete Training Kit
  • Coffee Break
  • Closing Ceremony

Gold Package

At least 3 people

USD1,850
  • 5-night stay in a 5-star hotel
  • Workshop or Program Participation
  • Airport Transfers
  • Customized Badge
  • Expert Mentorship (Private Sessions)
  • Supervision & Secretarial Services
  • Accredited Certificate of Participation
  • Complete Training Kit
  • Coffee Break
  • Closing Ceremony

Complete your registration

We will contact you within one business day to confirm.

Share this course

🔗 Short link
View packages and prices

✆