# Technical Training & Security Exercises

> Choose training on Rust, Substrate, and NEAR, or workshops, tabletop exercises, and key-ceremony rehearsals tailored to your systems.

Canonical page: https://www.guvenkaya.co/services/training-security-exercises

**Train on real findings. Rehearse real decisions.** Courses in Rust, Substrate, and NEAR, or a custom session using your systems, procedures, and roles.

## Formats

Choose a course in Rust, Substrate, or NEAR, or a custom session using your systems, procedures, and roles.

- **Secure-design workshops**: Challenge a real system and turn issues into design decisions.
- **Technical training**: Rust, blockchain, and smart-contract security tied to the stack.
- **Custody tabletops**: Practice key-management failures and high-impact decisions.
- **Key ceremonies**: Rehearse roles, evidence, exceptions, and recovery.
- **Incident exercises**: Test playbooks, escalation, and control behavior.
- **Executive workshops**: Practice digital-asset security decisions under realistic constraints.

## When to train or rehearse

- **Before a critical event**: A team is preparing for launch or a high-impact operation.
- **When procedures are untested**: The playbook exists but has not been exercised.
- **When engineers need deeper technical knowledge**: Training should connect directly to the actual stack and issues.
- **When leadership needs decision-making practice**: Decision-makers need experience under realistic constraints.

## How we build and run your session.

1. **Define what the team needs to practise**: Agree the technical skill, procedure, or leadership decision to exercise. Identify the participants, systems, and constraints that shape the session.
2. **Build the scenario and decision points**: Use your stack, roles, and threat model to design realistic events. Prepare the tasks and decisions participants will work through.
3. **Facilitate the session and capture observations**: Run the training or exercise, recording decisions, assumptions, and control gaps as the team works through the scenario.
4. **Debrief and prepare follow-up actions**: Review the observations with your team. Assign actions to address the gaps and prepare playbook material they can use after the session.

## Deliverables

- **Scenario design**: A session built around your systems and the decisions your team would have to make.
- **Facilitated session**: Technical training or exercise with clear decision points.
- **Follow-up actions**: What we observed, the gaps it exposed, and playbook material you can keep using.

## Engagement team

- **José C. Ramírez**, Specialist Advisor: Smart contract, protocol, application, Rust, EVM, and AI-assisted security analysis.
- **Timur Güvenkaya**, Founder & Partner: Rust-based and non-EVM systems, protocol security, architecture, infrastructure, and custody.

## Frequently asked questions

### Should we choose a course or a custom session?

Choose a course for Rust, Substrate and the Polkadot SDK, or NEAR. Choose a custom session for tabletops, key ceremony rehearsals, and decisions specific to your team.

### What are the courses based on?

The courses use findings from our published reviews. Watch the Rust and NEAR recordings below to see how we teach.

### Do you use our real systems and our real playbooks?

Yes. Custom exercises use your architecture, procedures, and threat model. We agree the scenario and access during scoping.

### Who should be in the room?

Include the people who would handle the event: signers and approvers for a key ceremony; engineering, operations, and decision-makers for an incident exercise.

### What do we need to prepare beforehand?

Share the relevant architecture and procedures, and agree the session’s objective. If you do not have a playbook, we can shape the session to help create one.

### What do we get afterwards?

You receive the scenario, observations, and follow-up actions with owners, plus updated playbook material where the exercise identified gaps.

## Related services

- [Signing & Custody Security Reviews](https://www.guvenkaya.co/services/signing-custody-security-review.md): Review key generation, signing approvals, key use, and recovery across MPC, HSM, multisig, and custody platforms.
- [Secure Architecture & Process Design](https://www.guvenkaya.co/services/secure-architecture-process-design.md): Design or assess critical systems, workflows, integrations, and operating controls before implementation or a major change.
- [Risk Assessment](https://www.guvenkaya.co/services/risk-assessment.md): Give leadership a prioritized view of where security risk concentrates and what to address first.

## Plan a workshop or security exercise.

Tell us who will attend, what they need to practice, and when. We will propose a course or custom session.

Discuss your scope: https://www.guvenkaya.co/contact