Evidence before theory
Logs, state, timestamps, routes, and configuration come before the story about what “must” be wrong.
alex@void:~$ ./operator --summary
SYSTEMS · NETWORKING · SECURITY · AUTOMATION
Aleksandr “Alex” Rupasov
I turn noisy symptoms into testable layers: endpoint, identity, network, service, and automation. Then I leave the result documented enough to repair again.
OPERATOR PROFILEVERIFIED
- experience
- 20+ years
- credentials
- 16 earned
- default mode
- verify first
- preferred state
- documented
OPERATIONAL LOOPrepeat until the evidence agrees
- 01Observecapture state before changing it
- 02Isolatereduce the failure to one layer
- 03Changeprefer the smallest reversible move
- 04Verifytest the outcome, not the intention
FIELD NOTE // 001
A system that only its author can repair is a temporary system.
alex@void:~$ whoami --verbose
OPERATOR PROFILE
Systems-minded IT
My background spans more than two decades of practical work across Windows systems, networking, end-user support, infrastructure, identity, and automation.
I work best where operations and troubleshooting overlap: establish what changed, identify where the failure actually lives, and make the repair repeatable.
Change one variable
Small reversible changes preserve causality and make rollback a real option.
Document the why
A command without context is a future incident waiting for an inconvenient hour.
Build for handoff
Reliable systems remain understandable after the original operator leaves the keyboard.
$ operating-principle
verify → isolate → change → verify again
alex@void:~$ stack --grouped --human
WORKING ENVIRONMENT
Practical stack, not keyword inventory
Systems
Windows 11 · Windows Server · Linux · Active Directory · Group Policy · Hyper-V
Endpoint
Microsoft Intune · SCCM · MDM/MAM · Microsoft 365 · Entra ID · Exchange
Networking
TCP/IP · DNS · DHCP · VLANs · VPN · routing/switching · VoIP
Automation
PowerShell · Python · Bash · Git · Docker · n8n
Security
Hardening · vulnerability management · certificates · identity · endpoint security
Lab
Azure DNS · Certbot · GitHub Pages · Ollama · local AI · agent workflows
user→identity→endpoint→network→service→evidence
# repeatability check
if (manual_twice) { document(); automate_when_sane(); }
alex@void:~$ credentials --verify --all
VERIFIED LEARNING RECORD
Credentials
16 verified credentials: 5 active CompTIA certifications and 11 Cisco networking and cybersecurity achievements.
165 CompTIA
11 Cisco
11 Cisco
01 CompTIA / active professional certifications
CompTIA A+ ceactive · expires 2029-06-11
CompTIA Network+ ceactive · expires 2029-06-11
CompTIA Security+ ceactive · expires 2029-02-06
CompTIA CIOSactive · expires 2029-06-11
CompTIA CSISactive · expires 2029-02-06
02 Cisco / CCNA pathway
CCNA: Introduction to Networksissued 2024-12-19
CCNA: Switching, Routing & Wireless Essentialsissued 2025-12-23
CCNA: Enterprise Networking, Security & Automationissued 2026-08-19
03 Cisco / networking + cybersecurity
Junior Cybersecurity Analyst Career Pathissued 2025-09-03
Network Securityissued 2026-06-02
Network Support and Securityissued 2026-05-12
Network Addressing & Basic Troubleshootingissued 2026-04-28
Networking Devices & Initial Configurationissued 2026-04-02
Networking Basicsissued 2026-03-20
Operating Systems Basicsissued 2026-02-17
Computer Hardware Basicsissued 2026-02-10
alex@void:~$ tail -n 6 ~/notes/field.log
FIELD NOTES
Useful fragments from the workbench
DNS
Delegate narrowly
DNS-01 does not require moving the whole zone. Delegate only the ACME challenge path and keep the authority boundary explicit.
OPS
Complexity has rent
One small service does not automatically need an empire of orchestration. Every layer must repay the failure modes it adds.
NET
Test layers separately
Name resolution, routing, transport, TLS, and application response are different checks. “The internet is down” is not a diagnosis.
AUTO
Automation needs an exit
A useful workflow exposes state, logs its decisions, and gives the operator a clean stop and rollback path.
LEARN
A study plan is a map
Walkthroughs refresh fundamentals and expose gaps. They do not replace the academic work of understanding why a result is correct.
IR
“Nothing changed” is an event
Configuration, timing, route, cache, dependency, certificate, policy, or assumption changed. Start collecting evidence.
alex@void:~$ ls -la ~/public-endpoints
PUBLIC ENDPOINTS
Elsewhere on the network
01
GitHubcode · experiments · repositories
github.com/AlexandrRupasov ↗
02
LinkedInprofessional timeline · technical posts
linkedin.com/in/alexandr-rupasov ↗
03
Credlyverified certifications · badges
credly.com/users/aleksandr-rupasov ↗
frameworknone
analyticsnone
runtime APInone
external fontsnone