Capabilities - Architecture, identity, testing
Security engineering
Controls enforced by the platform, not by a policy document.
What that means in practice
- Security architecture across cloud, hybrid, on-premises and OT
- Identity, secrets management, PKI and key management design
- Zero-trust segmentation and workload identity
- Penetration test scoping, interpretation and remediation planning
- Detection and response architecture; logging that survives an investigation
- Product security review for hardware and firmware, not only applications
- Depth
- Offensive and defensive experience: designing the controls, and having spent years finding the ways around them.
- Who I bring in
- Testing firms, detection and response providers, forensic specialists.
- Scoping this
- A short architecture review usually finds more than a long questionnaire.
Where I write about this
The newsletter follows what is changing here: one drawing, one decision worth revisiting, one tool used in anger, and what I am seeing across the network. Research worth reading gets cited when it changes a decision.
Adjacent
Rarely just one domain.
Most engagements touch three or four. These are the ones that usually come with it.
- R&D and special projects Feasibility, prototypes, hard problems
- RF, electromagnetics and analog Circuits, antennas, spectrum
- Semiconductor and programmable logic VLSI, ASIC, FPGA
- Embedded systems and device drivers Firmware, kernel, board bring-up
- Hardware manufacturing and supply ODM, DFM, certification
- Industrial automation and controls Robotics, SCADA, OT
- Software engineering Systems, automation, quality
- Cloud and infrastructure architecture Hybrid, containers, automation
- Governance, risk and compliance Audit, frameworks, fractional CISO
- Water, power and energy systems Treatment, generation, infrastructure
- Technical leadership and advisory Robotics, capital projects, family offices