I’m working toward becoming a penetration tester, and much of my learning involves web security, labs, tools and reading technical reports.
Alongside that, I’m building DaySec.org, an independent cybersecurity publication in English.
The idea is straightforward: publish security news and practical guides with enough context to help someone understand what matters. Which versions are affected? Does an attack require authentication? Has exploitation actually been reported? Where is the original advisory?
Those details shape how useful an article is.
DaySec covers vulnerabilities, security incidents, threats, AI security and practical learning topics. One recent example is a guide to applying OWASP threat modeling, using a hypothetical password-reset flow to connect possible abuse paths with security tests.
The site runs on WordPress. I manage the publishing workflow and use AI tools to assist with research and drafting. Opening the original sources, checking technical claims and making uncertainty visible are part of that process.
Working on the project gives me another way to practise explaining security concepts. Writing about a vulnerability means paying attention to its prerequisites, impact and limitations. It also gives me something concrete to maintain and improve as I learn.
There’s still plenty to work on, and I’d appreciate feedback from people who read or write technical security content.
If you take a look, what would make DaySec more useful to you?
Visit DaySec.org
Top comments (0)