Cybersecurity News & Diskussionsportal
⚡ tsecurity.de Intelligence
Your knowledge counts — guest article guidelines
Why your contribution belongs here
tsecurity.de thrives on the insights of its community: admins, analysts, pentesters and developers who work in IT security every day. A guest article is the most direct way to give that knowledge back — it appears instantly in the community feed, carries your name (or alias) as the author and counts towards your ranking among the community's top analysts.
What we look for
- Substance — analyses, workarounds, hardening guides, incident lessons learned or code snippets others can follow and apply.
- Verifiable claims — cite sources, CVE IDs or repositories; the form below has a dedicated field for references (source / GitHub link).
- Clear structure — Markdown is supported (headings, lists, code blocks). An opening sentence that sets the context helps every reader.
- Responsible disclosure — describe what the vulnerability is, who is affected and how to mitigate it. Working exploit code does not belong in a community article.
- No ads, no clickbait — articles exist for knowledge sharing, not self-promotion.
- Respect & privacy — no personal data of third parties, constructive tone even for critical findings.
Quick check before you submit
- Does the title say what readers will learn?
- Is the core insight visible in the first sentences?
- Are sources, CVEs or repositories linked?
- Does the text really contain no third-party personal data?
- Is the consent box ticked (section 4a of our terms + privacy policy)?
Your article is published to the community feed immediately and reviewed by the editors afterwards. Section 4a of our terms covers the rules for submitted content; the privacy policy explains how we handle your data.