Account security
Passwords are stored only as secure cryptographic hashes. Sessions use HttpOnly, Secure and SameSite cookies. State-changing operations are protected by permissions, validation, rate limiting and CSRF where required.
Protection built on boundaries
How we protect accounts, data and the monitoring process.
We describe the concrete safeguards around accounts, organization data and monitoring mechanisms without making promises that cannot be verified.
Safeguards in practice
Each area describes a mechanism that is actually part of the product. Technical detail stays concise without hiding the service limitations.
Organization isolation
User data belongs to organizations. Access is verified server-side and roles limit functions and information.
Monitoring security
URLs are normalized and checked. Private and local IPs are blocked. Ports, redirects, response time and downloaded size are limited to reduce SSRF risk.
Transmission and secrets
Communication uses HTTPS. Secrets are not placed in public code or sent to browsers.
Vulnerability reporting
Report suspected vulnerabilities to security@sitesentinel.pl with description, reproduction steps and possible impact. Do not publish details before analysis is complete.
Limitations
SiteSentinel helps detect operational issues but does not replace a security audit, penetration test, infrastructure administrator or legal consultation.
Found a vulnerability?
Send a description, reproduction steps and possible impact. Do not publish details before the analysis is complete.