Synaptic Four · Data and research

Security and data principles

How Synaptic Four handles access, data and systems when work is done on your infrastructure.

The important part first

Your data stays in your environment

The work happens in your cloud, on your premises, or in a separated network (VPC). Where the data is stored, and who operates it, stay with you.

Who has access

The founder, and permanent partners who are named beforehand.

Terms

Cloud
a service outside your own computer
MFA
a second check beside the password
VPC
a separated network in the client’s cloud

Principles

  • As little personal data as the task allows. When the task allows it, the work uses pseudonymised, aggregated or synthetic data rather than identifiable copies from the running system.
  • Access only for named tasks and periods. Access is per role and per task. Shared credentials are avoided.
  • Separate environments, clear boundaries, and a record of what touches what.
  • Architecture decisions are written down.
  • Retention only as long as needed. Work products stay only as long as delivery and the agreed handover need them.

How this is done in a project

How this is done in a project
QuestionAnswer
Who sets up access? Your organisation. Access is per role and per task, and shared credentials are avoided.
How are important accounts protected? With a second check beside the password (MFA). Broad administrator rights only with a written reason.
Which data is used? Preferably data from outside the running system. If real data is needed, that is written into the agreed scope.
What happens at the end? Credentials are rotated or withdrawn. Working copies are deleted or returned under your rule.
Confidentiality?
Confidentiality is agreed when you ask for it. For personal data there is a processing agreement.
What happens in a security incident?
Synaptic Four informs you without undue delay, at the latest 24 hours after the incident becomes known, and supports the investigation. Duties to report to authorities stay with your organisation.

Responsibilities

Your organisation operates the infrastructure and is responsible for backups and users. Synaptic Four works within the scope agreed for the task.

What is not there (yet)

Synaptic Four has no certification such as ISO 27001. The practices described are ways of working. They do not replace a review by an independent body.

Round-the-clock operation is not offered.

For health data, critical infrastructure or strict separation, extra safeguards are fixed before the work begins.

Does your information-security team have questions before an engagement?

Ask a question