
Connector
Synology DSM
API credential, entered client by client.
The operating system of Synology NAS appliances. Vigicap authenticates through Synology's own published login API and reads the list of APIs the NAS exposes, which names the backup applications installed on it (Hyper Backup, Active Backup for Business, Snapshot Replication). Synology's published API exposes neither the date of the last successful backup nor any restore test: this connector therefore never proposes more than level 2 on the ReCyF objective « Sauvegardes et restauration », and that ceiling comes from the vendor's API, not from the client's backups.
01
What to create in the tool
The access is created in Synology DSM, not in Vigicap.
Where to generate it
Créez un utilisateur DSM dédié, sans droit d'administration, et désactivez la double authentification pour ce compte (l'API de connexion de Synology la refuse : codes 403/406). L'adresse demandée est celle de DSM, port 5001 en HTTPS par exemple. Le NAS doit présenter un certificat TLS valide et reconnu — le certificat auto-signé installé par défaut sera refusé par Vigicap (DSM sait obtenir un certificat Let's Encrypt : Panneau de configuration > Sécurité > Certificat).
Minimum role
Créez un utilisateur DSM dédié (Panneau de configuration > Utilisateur et groupe) sans droit d'administration et sans accès aux dossiers partagés : ce connecteur n'appelle que SYNO.API.Info et SYNO.API.Auth. La double authentification doit être désactivée sur ce seul compte de service — DSM refuse une connexion par API lorsqu'elle est exigée (codes 403 et 406).
Taken from the vendor's own role model, and checked before publication.
02
What to enter in Vigicap
- Compte DSMsecret
Utilisateur DSM dédié, sans droit d'administration.
vigicap
- Mot de passesecret
Mot de passe de ce compte. La double authentification doit être désactivée sur ce compte.
03
Per-client routing
The connection is made client by client: one credential per client, entered on that client's record. Nothing is shared between two clients, and disconnecting one leaves the other untouched.
04
What it does, and what it does not do
ISO 27001 controls covered
This connector's readings feed ${n} Annex A controls — derived from the ReCyF objectives above, not entered by hand.
- 5.29 Information security during disruption
- 5.30 ICT readiness for business continuity
- 5.33 Protection of records
- 8.6 Capacity management
- 8.13 Information backup
- 8.14 Redundancy of information processing facilities
ReCyF objectives it pre-fills
A reading feeds one objective of the ANSSI ReCyF framework. It PROPOSES it: the level only counts once a consultant has confirmed it.
- #13 Continuité et reprise d'activitéBusiness continuity and recovery
Read-only
Vigicap writes nothing to the tool while reading.
How Vigicap handles your credentials.
Verification
The tool is an appliance operating system with no vendor-supported container image, so there is no throwaway instance to drive it against. This is not “not yet done”; it is a verification nobody will complete by finding an afternoon.