PRACTICE / SELECTED WORK
In IT administration, I connect configuration, practical checks and documentation. These examples show my contribution and the specific scope of verification.
From backup to restored service.
01 / RECOVERY
Container restored. Services checked.
As part of backup administration, I participated in restoring a monitoring container from local and external backups. Each restore was followed by startup and service checks, with the results recorded in documentation.
Documented outcomeThe container started in both tests, and the checked monitoring services were running.
Verification scope: Verification covered one selected instance and the state of its services. The tests do not establish recovery of the entire environment or databases, or delivery of every alert.
02 / PERMISSIONS
Send a backup. Without permission to delete it.
For external backups, I worked with separate permissions for sending backups and restoring them. Verification included an attempt to delete a snapshot using the sending permission.
Documented outcomeDeletion was denied, and the snapshot remained intact.
Verification scope: The result confirms a specific permission boundary. It does not establish absolute backup immutability or protection against every attack scenario.
03 / NETWORK
Separate traffic by its purpose.
I administered selected rules between network zones and checked communication between them. I recorded configuration and selected access test results in operational documentation.
Documented outcomeThe operational segmentation had documented rules and selected verified communication paths.
Verification scope: This covers administration and checks of selected parts of an existing network. It does not claim a complete test of every path or sole original design of the entire network.
04 / UPDATE
Checks before the change. Verification after it.
With AI assistance, I worked on a PowerShell update procedure for a vendor application: package and integrity checks, a backup before the change, and subsequent startup and version checks. The procedure was refined based on an actual run.
Documented outcomeOne production upgrade is documented, including application startup, an HTTP response and the resulting version. Initialization detection was adjusted to match the observed log format.
Verification scope: A subsequent upgrade after this adjustment is not documented. Checking the backup archive was not a database restore test; automatic rollback is unconfirmed.
05 / CLOUD
A review with evidence and open points.
I mapped cloud identities, roles and licences and reviewed authentication and sharing settings. The work included checking selected TOTP sign-ins and restoring a test document from the Recycle Bin.
Documented outcomeThe basic configuration review was closed with recorded reservations. The selected sign-ins and test document recovery succeeded.
Verification scope: This was not a certified security audit or confirmation of organisation-wide MFA enforcement. The document test does not cover complete recovery of cloud data.
06 / DOCUMENTATION
From an operational wiki to traceable records.
I configured an internal wiki, prepared its page structure and controlled access to documentation. I supplied technical information and checked corrections while working on an AI-assisted draft asset register and materials for external security assessment.
Documented outcomeThe operational knowledge base had separated permissions. Working records were prepared for asset tracking and gap assessment.
Verification scope: Operating the wiki and preparing draft records are distinct outcomes. Formal approval of these records and publication of all newer audit texts in the wiki are unconfirmed.
These anonymised examples describe selected activities within a specific scope. Individual tests do not cover the entire environment. Technical records and internal configurations remain private.