Newsroom directory
HackWatch uses named editor profiles and newsroom review to organize public reporting by specialty while keeping responsibility, source quality and update ownership visible to readers.
This page is the public author directory for HackWatch. It shows who maintains each reporting lane, what each editor covers and where readers can review accountability, editorial standards and credential-track disclosures.
HackWatch is an independent cybersecurity publication. Our editorial coverage is maintained by named editors. We are currently expanding our editorial team with verified cybersecurity professionals; credential disclosures will be updated on individual author pages as editors are confirmed.
Founder of HackWatch.io and WEB-NET; Editorial Reviewer
Artur Ślesik is the founder of HackWatch.io and WEB-NET, a real named reviewer with 17+ years of experience building and maintaining web portals.
Focus: Secure web portals, phishing prevention, user-facing recovery guides and practical web-security review
Open editor profile
Infrastructure Security Editor at HackWatch.io
Marcin Pocztowski is the owner of MMPS and an infrastructure security editor for HackWatch. His public technical record spans 20 years, from Security+ evidence dated January 2006 through Juniper, Cisco and RHCSA records, and he reviews server, network and vulnerability-response coverage for source accuracy and practical remediation.
Focus: Server and network hardening, vulnerability response, patch prioritization and infrastructure security review
Open editor profileOpen a reviewer profile to see who owns a topic lane, how coverage is maintained and which alert categories are tied to that coverage area.
Every editor profile explains editorial responsibility, credential-track standards, visible methodology and how verified credentials are disclosed.
Each profile links directly to recent documented alerts so readers can judge consistency, quality and topical depth for that coverage area.
This directory helps readers looking for HackWatch authors, cybersecurity editors and newsroom ownership understand who maintains phishing alerts, breach coverage, vulnerability reporting and recovery guides.
HackWatch is structured like a security newsroom team with real reviewer profiles, visible bylines, source standards and public links to recent work so readers can evaluate consistency and trust.
Use these reviewer profiles to jump into people responsible for phishing response, identity recovery, exploited vulnerabilities, threat intelligence, malware operations and practical incident workflows.
Public certifications, employer history and external reviewer credentials are shown only when they can be tied to a verified named contributor or reviewer.
Editors prioritize primary advisories, CERT notices, government guidance, named researcher reporting and corroborating public records over derivative summaries.
Article updates and correction requests are handled through the public correction process described in the HackWatch editorial policy.
Contributor author template
New contributor profiles are created only after an accepted publication and author approval. Profiles use real names, confirmed links and visible editorial status. Contributors cannot publish directly.
Display name, country or region when approved, student or junior contributor status and verified external links.
Focus area, safe frameworks used now, public sources monitored and editor-reviewed topics.
Role is Contributor by default. Editor approval is required before publication, updates or profile claims.