Security work that starts with a padlock icon has already chosen the wrong representation. The useful representation is a boundary: what is inside, what is outside, and which identities are allowed to cross.
Skyneski approaches security as research and engineering. That means asking how a system fails, which assets matter, and which controls are actually in the design rather than in a slide.
Different surfaces, same discipline
Infrastructure security and IoT security look different and rhyme. A server has an owner and a patch window. A device in the field may have neither. Both need an explicit threat model. Both need monitoring that distinguishes a fault from an intrusion often enough to be useful.
Risk analysis is the adult version of a security page. Some risks are reduced. Some are accepted and written down. Pretending all of them are closed is how trust gets spent.
What we will not claim
Skyneski does not claim certifications it does not hold. A future audit is not a current control. If a collaborator needs a specific assurance, the honest answer is a conversation about what exists today, not a badge.