Sole Owner of Enterprise Access Reporting Through the COVID-19 Disruption
Kept enterprise access and operational reporting uninterrupted throughout the COVID-19 remote transition, for a VPN serving 60,000 corporate users.
The Problem
During COVID-19, Prudential Financial moved its entire workforce to remote operations within weeks. The remote-access platform became the front door to the company, and the access and operational reporting built on it had to keep flowing to leadership, security teams, and global business partners without a gap.
Leadership needed dependable operational visibility to confirm continuity and security compliance across the enterprise.
There was significant operational risk around continuity and accuracy. A gap in that reporting would have left leadership without a view of the remote transition at the moment it mattered most.
The Approach
Served as the sole technical owner of the access and operational reporting for the remote-access platform during the disruption period: the recurring reports to global business partners, the leadership visibility reports, and the administrative automation that kept the operations team ahead of the queue.
Built and maintained access reporting that gave leadership timely operational visibility and helped security teams investigate anomalies.
Maintained accuracy, compliance, and timeliness of reporting across all stakeholder groups while operating without the normal support structures of in-office collaboration.
The Impact
- Kept access and operational reporting uninterrupted during the COVID-19 remote transition, for a VPN serving 60,000 corporate users
- Kept recurring reports flowing to global business partners throughout the disruption
- Automated over 200,000 administrative actions so operations teams could focus on exception handling
- Access reporting gave leadership dependable operational visibility throughout the crisis period
- Demonstrated solo ownership of a mission-critical reporting function under high-pressure, high-visibility conditions
Evidence
- Private (employer)Enterprise access and operational reporting through the 2020 disruption (employer work, not linkable)
Related
Your CI was green and the pipeline produced nothing: a nine-day silent failure
A Windows Task Scheduler default fed my Claude Code memory pipeline its own transcripts for nine days: 21,264 junk sessions, 38 GB of exhaust, and an 18,428-session backlog that was really 1,924. The durable fix: postconditions that outrank green dashboards.
A One-Day Security Baseline for a Solo Fleet
You cannot out-staff a security team when you are the whole team. But the failures that actually end a solo operation are a short, known list, and each has a cheap defense you set up once. Here is the catastrophic floor I stood up in an afternoon.
Institutional Memory for a Team of One
A team holds its hard-won knowledge across many heads. A solo operator holds it in one, and that one forgets. The fix is to externalize memory into structured records the tools read by default, so the system remembers what the person cannot.