1. Security Philosophy
Neodymium conducts analysis on sensitive sectors, including geopolitics, defense systems, and sovereign computing infrastructure. Given the nature of our reporting, maintaining a highly secure, resilient, and integrity-verified web portal is of paramount importance to protect both our editorial pipelines and our users.
2. Transport & Infrastructure Security
We enforce strict security protocols to prevent interception, modification, or injection attacks on our Site traffic:
- Strict Transport Security (HTTPS): All connections to Neodymium are encrypted using industry-standard TLS (Transport Layer Security) via GitHub Pages and custom DNS routing.
- Static Deployments: The Site operates as a static site generated from secure, offline database backups. Because we do not run runtime databases or dynamic query engines (like SQL/PHP), typical server-side injection vectors are entirely eliminated.
- DNS Protection: We use advanced DNS protection and Cloudflare caching to prevent DDoS attacks, DNS poisoning, and server overload.
3. Third-Party Libraries & Dependencies
Our automation frameworks (such as sitemap generators, RSS compilers, and HTML rendering scripts) are audited regularly. We keep all core library dependencies (e.g. Trafilatura, Jinja2, Google Generative AI Python library) updated to the latest stable versions to prevent exploit vectors in our backend pipeline.
4. User Data Protection
Neodymium gathers minimal user data, primarily email addresses for newsletter delivery. These email databases are managed under strict access control panels with two-factor authentication (2FA) enabled on all administrative accounts. We do not store financial payment information on our servers; all subscriptions are handled via PCI-compliant premium payment networks (such as Stripe).
5. Vulnerability Disclosure Policy
We welcome security researchers and analysts who identify vulnerabilities to report them responsibly. If you discover a security vulnerability in our domain, please email us directly at neodymium.world@gmail.com.
In your report, please include:
- A detailed description of the vulnerability.
- Steps to reproduce or a proof of concept (PoC).
- The potential impact of the issue.
We request that you do not publish or share the vulnerability details with third parties before we have had a reasonable timeframe to mitigate and resolve the issue.