Secure Development Lifecycle (SDL) & IEC 62443-4-1 Programme
- Secure product development lifecycle design aligned to IEC 62443-4-1 practices: security requirements, threat modelling, secure design, secure implementation, verification, defect management, release management
- Gap assessment against current practice and roadmap to IEC 62443-4-1 certification
- Developer training and secure-coding standard integration
- Security tool integration into CI/CD: SAST, SCA (software composition analysis), SBOM generation, secrets scanning, fuzzing
- Release-gate definition and security-approval workflow
Threat Modelling & Security Requirements
- Device-specific threat modelling (STRIDE, PASTA, or domain-specific frameworks) against realistic adversary profiles
- Security-requirements engineering aligned to IEC 62443-4-2 component SL targets (SL1–SL4)
- Protection-profile design for Common Criteria evaluation where markets require
- Abuse-case analysis, misuse-case documentation, and attack-tree development
Firmware & Embedded Software Architecture
- Secure boot architecture: root-of-trust selection, signed boot chain, anti-rollback, recovery paths
- Runtime protections: memory-safety strategy, stack canary, ASLR where architecturally feasible, control-flow integrity
- Cryptographic architecture: algorithm selection, key-storage, key-lifecycle, post-quantum migration planning
- Secure firmware update (FOTA/FOTA-delta): signed updates, atomic installation, A/B partitioning, signed-manifest integrity
- Secure provisioning: factory personalisation, device-identity injection, HSM-backed key generation
- Debug-interface hardening: JTAG/SWD disablement strategy, lifecycle-based access control, anti-tamper measures
- Isolation and sandboxing: TEE integration (TrustZone, SGX, SEV), process isolation, capability-based security models
SBOM, Vulnerability Handling & CVD
- Software bill-of-materials (SBOM) generation and maintenance: SPDX, CycloneDX, VEX documents
- Vulnerability-handling process aligned to ISO/IEC 30111 and IEC 62443-4-1 DM practice
- Coordinated vulnerability disclosure (CVD) programme design: security.txt, PSIRT setup, disclosure timelines, bug-bounty structure
- CVE-to-product triage: the real exploitability of a public CVE against this device, this configuration, this use case
- Security update and patch management: release cadence, customer-notification architecture, support-lifecycle alignment
Automotive Cybersecurity (UN R155/R156, ISO/SAE 21434)
- Cybersecurity Management System (CSMS) design aligned to UN R155 and ISO/SAE 21434
- Software Update Management System (SUMS) design aligned to UN R156
- TARA (Threat Analysis and Risk Assessment) methodology and execution
- Type Approval preparation and technical-service liaison
- Post-type-approval vulnerability monitoring and response
Medical Device Cybersecurity (FDA 524B, EU MDR)
- Premarket cybersecurity submission preparation aligned to FDA 524B and Premarket Cybersecurity Content guidance
- Secure Product Development Framework (SPDF) aligned to AAMI TIR57
- Risk-management integration with ISO 14971 safety risk management
- Postmarket cybersecurity: monitoring, patching, and notification under FDA postmarket guidance
- EU MDR Annex I cybersecurity alignment and MDCG 2019-16 technical documentation