OT/ICS Security
My OT/ICS security interest is built on a practical foundation: nearly five years of building operations experience, academic ICS/SCADA lab exposure, and cybersecurity training.
I do not present myself as a senior OT/ICS specialist. I present OT/ICS as a developing specialty connected to real infrastructure operations, cyber-physical risk, availability, and security workflow coordination.
Why this section matters: My background gives me a practical understanding that availability, documentation, coordination, and recovery matter alongside technical security findings.
Primary Evidence#
Critical Infrastructure Operations Foundation#
My strongest OT/ICS-relevant professional foundation.
Nearly five years in building engineering, developing operational ownership, documentation discipline, stakeholder communication, and continuity-focused thinking.
ICS/IT-OT Application-Level DoS Lab#
Academic OT/ICS lab work focused on application-level disruption, visibility loss, operational impact, availability, and recovery validation.
This page shows how I connect cybersecurity concepts to operational disruption and recovery.
ServiceNow SecOps Connection#
My ServiceNow SecOps direction connects naturally to OT/ICS environments because operational security work depends on ownership, escalation, documentation, remediation tracking, validation, and closure.
What My Background Adds#
How This Fits My Main Career Direction#
My primary professional lane remains ServiceNow SecOps and Vulnerability Response.
OT/ICS matters because many operational environments need better ways to turn security findings into practical work:
- clear ownership
- remediation coordination
- operational risk review
- maintenance-aware planning
- exception handling
- validation
- closure
- reporting
That is where my building operations background, cybersecurity education, and ServiceNow SecOps direction connect.