This page answers a simple question: what can be checked, not merely claimed.
Use it as a fast proof hub for hiring, collaboration, GRC discussions, or evaluation of technical thinking quality. If time is short, start with the Leadership Profile, Evidence Map, Stats, and Learning Roadmap.
Quick Evaluation
| Signal | What to check | Why it matters |
|---|---|---|
| Public profiles | GitHub, LinkedIn, TryHackMe, pwn.college | Confirm external context and practical traces |
| Published materials | Articles, maps, decision records, roadmap | See thinking style and explanation quality |
| Evidence discipline | sources, boundaries, assumptions, safety labels | Separate facts from conclusions and claims |
| Decision thinking | finding, risk, control, decision, next step | Evaluate whether technical work leads to action |
| Trust layer | privacy, security, AI, editorial, accessibility | Check maturity of the public system |
Public Profiles
- GitHub: github.com/VasiaZozulia - code, scripts, documentation, and materials that may support publications.
- pwn.college: pwn.college/hacker/48097 - hands-on security practice.
- TryHackMe: tryhackme.com/p/VasiaZozulia - controlled security rooms and learning paths.
- LinkedIn: linkedin.com/in/VasiaZozulia - professional context and contact.
Strongest Artifacts
- Leadership Profile - short review for leaders, hiring managers, and partners.
- Evidence Map - competencies, evidence, team value, and gaps.
- Stats - library health, quality, freshness, audiences, safety, and backlog.
- Learning Roadmap - direction of growth, current focus, and expected evidence.
- How to Read a Security Lab Write-up - boundaries, safety labels, and the proper use of lab material.
- Finding → Risk → Control - an example of turning a technical observation into a decision.
- AI-Assisted Technical Note - a workflow for validating AI-assisted output.
- Linux Permissions as a Security Control - a technical topic framed as a control.
- From Vulnerability to Business Risk - a short executive/GRC format.
Who This Page Serves
| Audience | Fast route |
|---|---|
| Hiring manager or tech lead | Profile → Evidence Map → GitHub |
| Security / infrastructure practitioner | Practice → security materials → Stats |
| GRC / audit / compliance | Evidence Map → Decision records → Trust Center |
| Client or partner | Services → Collaboration → Contact |
What Counts as Evidence
- public profile, repository, or published material;
- description of environment, tools, scope, and assumptions;
- commands, outputs, screenshots, or logs when safe to publish;
- clear separation of facts, assumptions, limitations, and conclusions;
- connection between a technical finding and a risk, control, or decision.
What Still Needs Strengthening
- more materials with primary-source evidence in front matter;
- more short executive summaries for GRC and leadership readers;
- more practical artifacts where commands, results, or a decision trail can be shown safely;
- regular refreshes for older materials so technical claims do not age quietly;
- clearer links between articles, roadmap, evidence map, and services.
Interpretation Limits
This portfolio does not replace an interview, practical assignment, reference check, or formal experience audit. Read it as a public evidence base: it shows direction, discipline, thinking style, and communication quality.
For the competency map, see Evidence Map. For the executive view, see the Leadership Profile. For current focus, see Now.
