I am a Cybersecurity Architect with 14 years of building and defending enterprise and critical infrastructure networks. My work is network access control with Cisco ISE and TrustSec, segmentation of industrial networks along IEC 62443 and NIST SP 800-82 lines, detection with flow analytics and NDR, and campus fabrics on Catalyst Center and SD-Access.

These are field notes from that work, written without any client in them. The work page shows what I have delivered. The tools page lists the open-source, read-only tools I wrote for it.

Contact: arkadiy@ayrapetov.co · github.com/a-ayrapetov

Posts

  • Moving switches to ISE TACACS+ without locking yourself out

    Moving switch logins from local accounts to Cisco ISE TACACS+ is routine work, and it is also the change most likely to lock you out of your own network. On one migration of older switches, a method list in the wrong shape cost a full day and three lockouts. The failure looked exactly like a bad password every time, which is why it took so long to see.

  • Inventory an OT network without sending it a single packet

    Every OT security program starts with the same question: what is actually on this network? On an office network the usual answer is a scan. On a network full of controllers, drives, HMIs and remote terminal units, a scan is the one answer you cannot use. Older controllers and protocol stacks can stop responding or fault when they are probed, and a scan during operations is a change nobody approved.

  • Cutting NDR alarm noise without going blind

    A noisy detection platform is a smoke alarm that goes off every time someone makes toast. After a week nobody looks up, and the one real fire gets the same shrug. Flow analytics and network detection platforms on large networks often raise thousands of alarms a day. Most of them come from a handful of rules and a handful of hosts nobody ever classified.

  • Closing access ports on industrial switches, one port at a time

    Closing access ports on an industrial network is like changing the locks in a building that never closes. Every door has to keep working for the people already inside while you work on it. The devices on these ports (cameras, intercoms, sensors, controllers, signs) mostly cannot run 802.1X, so they get MAC Authentication Bypass. In closed mode, a port passes nothing until the policy server says yes. One wrong group, one stale MAC address or one device that has not spoken yet, and something that matters goes dark.

  • An AI assistant on a production network that never gets a session

    I use an AI assistant on almost every engagement now: switch and controller work, ISE policy, monitoring platforms, industrial networks. It has never once held a session on a client device, and that is the reason it is safe to use at all.

  • When TrustSec looks like a routing problem

    The ticket said the domain controllers were down. They were not. They answered DNS, Kerberos and LDAP all day. They just would not answer a ping, and every monitoring check, everyone’s first test and half the troubleshooting runbooks start with a ping. Two hours of looking at routing tables later, the cause turned out to be one cell in a TrustSec policy matrix.

  • Triaging interface errors across a whole switch stack

    Most physical-layer problems announce themselves in show interfaces long before a user opens a ticket. The trouble is volume: a stack of four 48-port switches is close to two hundred interfaces, and nobody reads two hundred counter blocks carefully. Here is the triage order I use, and the tool I wrote to do the reading for me.

  • The ISE certificate that takes 802.1X down on a Tuesday

    Certificate expiry is the most predictable outage in network access control, and it still catches teams every year. The expiry date has been printed on the certificate since the day it was issued. What fails is the process around it.

  • A network hardening assessment in two read-only steps

    Clients ask for a hardening review in one of two moods: before an audit, or after a scare. Either way they want the same deliverable: what is weak, how bad it is, and exactly what to change. Here is the workflow I use, built so that nothing touches production except one read-only command.

  • Configuration drift as an audit control, not a chore

    Every network I have inherited had changes nobody could explain. An ACL line added during an outage and never removed. A trunk carrying a VLAN that was supposed to be retired. A port left in a test VLAN. None of these are dramatic, and all of them are how segmentation quietly erodes.

subscribe via RSS