Security
How Junsu protects your data
Junsu holds risk matrices, audit evidence and personal data about third parties. This page sums up how that information is protected.
Isolation per organisation
Each organisation is separated inside the database with PostgreSQL row-level security, forced and failing closed: a request that carries no organisation sees no data.
Mandatory MFA
Sign-in goes through AWS Cognito with a mandatory TOTP second factor. The browser only keeps an HttpOnly session cookie, never a token.
Permissions by role, phase and area
Compliance officers, area owners, external certifiers and platform administrators each see and do only what their role allows.
Audit trail
Changes are written to an append-only audit log and every decision keeps its justification. The methodology is versioned, so history never changes by itself.
Hosting and encryption
Junsu runs on AWS in the Ireland region (eu-west-1). Documents and sensitive information are stored encrypted.
Checked uploads
Every uploaded file is scanned for malware before it is accepted.
AI that proposes, people who decide
AI never closes a step on its own. The text of uploaded documents and external pages is treated as data, never as instructions.
Security questions
Have a security question, or found a vulnerability? Write to us at Contacto@junsu.es.