SOCTitan

Version 1.1 · November 2026

Technical and organisational measures

The security measures SOCTitan applies to personal data processed on behalf of customers under our Data Processing Agreement, aligned with Article 32 GDPR. This page is an expanded version of Annex 3 of the DPA. If the two differ, the DPA prevails.

Operator: Herr Godfrey Mwasanje c/o Block Services, Stuttgarter Straße 106, 70736 Fellbach, Deutschland Email: contact@soctitan.com

1. Approach to security

The processor implements measures appropriate to the nature, scope, context and purposes of the processing, and to the risks of varying likelihood and severity for the rights and freedoms of natural persons. Measures are reviewed periodically and may be updated, provided the level of security is not reduced.

2. Pseudonymisation and encryption (Art. 32(1)(a))

  • Encryption in transit. All connections to the website, the portal and its interfaces use TLS 1.2 or higher, enforced by HTTPS redirection and HTTP Strict Transport Security. Connections from our server to the intelligence provider use TLS with full certificate verification.
  • Encryption at rest. Secrets stored by the application (the intelligence provider key and users’ authenticator secrets) are encrypted with authenticated encryption (XSalsa20-Poly1305 via libsodium, or AES-256-GCM). Full search results are held for at most 20 minutes, encrypted with a key specific to the user account, and are then deleted.
  • Password storage. Account passwords are stored only as salted hashes (Argon2id, or bcrypt where Argon2id is unavailable). Plaintext passwords are never written to disk or logs.
  • Device binding. Accounts can be bound to one device by a random 256-bit device key. Only a SHA-256 hash of the key is stored (see section 6.1.1).
  • Credential isolation. Connection credentials for upstream intelligence sources are stored only on the server, outside the web-accessible folder, and are never transmitted to the browser. All upstream requests are made by the server.

3. Confidentiality, integrity, availability and resilience (Art. 32(1)(b))

  • Confidentiality. Access to personal data is restricted by role (administrator, partner, customer user) and by per-service permissions, checked on the server for every request. Partners can only see and manage their own client accounts. Showing leaked passwords in clear text and exporting results are separate permissions. Authenticator codes are mandatory for administrators and partners.
  • Integrity. Every sign-in, search, password reveal, export and administrative change is written to an audit log. No screen in the application allows audit entries to be edited or deleted. All forms are protected against cross-site request forgery, and pages cannot be embedded by other sites.
  • Availability. The platform runs on managed web hosting in the EU/EEA with the provider’s redundant power, connectivity and monitoring.
  • Resilience. Rate limits per network, per account and per day protect the platform and its upstream sources from abuse. Errors are logged privately; visitors only see a neutral message.

4. Ability to restore availability and access (Art. 32(1)(c))

The hosting provider’s backups of the web space and the private data folder support restoration after a physical or technical incident. Restoration is carried out on a best-effort basis. Given its present operational scale and the absence of a 24/7 service commitment, the processor does not currently commit to specific recovery time (RTO) or recovery point (RPO) targets.

5. Regular testing, assessing and evaluating effectiveness (Art. 32(1)(d))

The processor monitors security advisories relevant to the components in use (PHP, the web server and the bundled libraries), applies security-relevant updates promptly after assessment, tests changes on a separate test copy before they are uploaded to the live site, and reviews access rights periodically.

6.1 Access control and authentication

  • Role-based access control and per-service permissions restrict access to personal data to authorised users on a need-to-know basis.
  • Accounts are created only by the operator or an authorised partner; there is no public self-registration.
  • Each account has a defined validity period and stops working automatically when it ends; open sessions end on the next request.
  • Sessions end after 30 minutes of inactivity and after 8 hours at the latest, and are tied to the browser that opened them.
  • Six wrong passwords lock an account for 15 minutes; sign-in attempts are limited per network and per username.
  • Authenticator codes (TOTP, each code usable once) are mandatory for administrators and partners and can be required for any user.
  • Multi-factor authentication is used for the operator’s own access to hosting, email and other infrastructure.

6.1.1 Device recognition and device binding

  • What is used: a random 256-bit device key, generated by the server and stored in a secure, HTTP-only, same-site cookie in the user’s browser. No characteristics of the device or browser are read or combined.
  • Pseudonymisation: only a SHA-256 hash of the key is stored. The key cannot be derived from the hash.
  • Storage: the hash is held in a device register linked to the user account, with a label such as “Chrome on Windows”, the IP address and the dates of registration and last use. Users can see their own devices; administrators can see and reset the devices of the accounts they manage.
  • Enforcement: for device-locked accounts, every sign-in and every request checks the key against the registered device. Other browsers are refused until an administrator resets the binding. The device is bound only after all sign-in steps, including authenticator codes, have succeeded. Resets are recorded in the audit log.
  • No advertising identifiers, browser fingerprinting or client-installed software are used, and the key is never used for marketing, profiling or tracking. Device entries are deleted when the account is deleted.

6.2 Network and infrastructure security

  • HTTPS enforced for all connections, with HSTS.
  • A strict content security policy: pages load only scripts, styles and fonts from soctitan.com. No third-party code runs on the site.
  • Program code, configuration, database and logs cannot be opened from the web. Only the single application entry point can be executed.
  • The database and secrets are kept in a private folder outside the public web folder wherever the hosting allows it, and are otherwise blocked from web access.
  • Hosting with data residency in the EU/EEA.

6.3 Application security and change management

The application source is kept under version control by the operator. Changes are tested on a separate test copy and then uploaded to the live site over an encrypted connection (SFTP). The live site contains no development tools or test data.

6.4 Logging and monitoring

  • An audit log records sign-ins, administrative actions and search metadata (time, account, service used, action and IP address).
  • Audit logs are kept for three (3) months and then deleted automatically.
  • Free checks on the public website are logged for abuse prevention and deleted after 90 days.
  • Full search results are kept for 20 minutes only, encrypted, so that the user can reveal or export them, and are then deleted. Exports are generated on request and are not stored on the server.
  • No advertising, marketing or cross-site tracking technology and no analytics cookies are used.

6.5 Vulnerability and patch management

The processor follows security advisories and CVE disclosures for the technology in use. Security-relevant updates are reviewed and applied as part of regular maintenance, prioritised by severity and exposure.

6.6 Backup and recovery

Backups are made through the hosting provider’s backup system in the EU/EEA. Restoration is performed on a best-effort basis as described in section 4.

6.7 Physical security

Physical security of the production infrastructure is provided by the hosting provider’s EU/EEA data centres, including access control, environmental controls, fire suppression, redundant power and connectivity and secure disposal of media. The processor operates no premises that house production data.

7. Personnel and organisational measures

SOCTitan is operated by Herr Godfrey Mwasanje as a single-operator business. The operator is the only person with access to production systems and to personal data processed on behalf of the controller, and is bound by statutory and contractual confidentiality obligations. No employees, contractors or interns currently have such access. Anyone granted access in future will be bound by written confidentiality commitments.

8. Sub-processor management

Sub-processors are engaged only under data-protection obligations equivalent to those in the DPA. The current sub-processors are the web hosting provider (servers, database and email) and the licensed breach-intelligence provider. Changes are notified to the controller at least 30 days in advance, and the controller may object on reasonable data-protection grounds.

9. Incident response and breach notification

  • Detection. Incidents are detected through the audit log, error logs and review of unusual activity, such as repeated failed sign-ins or blocked devices.
  • Reporting channel. Suspected vulnerabilities or incidents can be reported to security@soctitan.com or contact@soctitan.com. Reports made in good faith are handled under a coordinated disclosure approach.
  • Notification to the controller. The processor notifies the controller of any personal data breach affecting the controller’s data without undue delay and in any event within 24 hours of becoming aware of it, with a substantive update containing the information required under Article 33(3) GDPR within a further 48 hours.
  • Cooperation. The processor assists the controller with its own notifications to supervisory authorities (Art. 33) and affected persons (Art. 34), taking into account the nature of processing and the information available.

10. Periodic review

These measures are reviewed periodically and may be updated, provided the level of security is not reduced. Material changes affecting the controller are communicated in accordance with the DPA.