Connector
ServiceNow
Outbound ticketing integration: Vigicap files tickets into it.
Your actions go into ServiceNow as records, in the table you choose (incident by default) and under the client's company. The status is then read back: resolved or closed in ServiceNow, Vigicap proposes closing the action and never closes it by itself. No ReCyF level is proposed. Pushing a ticket does not measure a client's posture.
01
What to create in the tool
The access is created in ServiceNow, not in Vigicap.
Where to generate it
The instance URL is https://your-instance.service-now.com. Use a dedicated account holding both the itil and snc_basic_auth_api_access roles (without the second, ServiceNow refuses basic authentication and answers 401), allowed to write the company field — otherwise the ticket is created but attached to no client. Restrict it by ACL to the target table. The company sys_id comes from core_company.
Minimum role
Compte applicatif ServiceNow en authentification de base. RÔLES : `itil` (création et relecture dans la table visée, `admin` n'est pas nécessaire) et `snc_basic_auth_api_access`, exigé depuis que ServiceNow restreint l'authentification de base aux comptes qui le portent — sans lui, chaque appel répond 401 « User is not authenticated » quel que soit le mot de passe, car l'identifiant n'est même pas évalué. DROIT D'ÉCRITURE SUR `company` : sans lui, ServiceNow crée le ticket, répond 201 et ignore le champ en silence ; le ticket n'est alors rattaché à aucun client et le routage par client ne sert à rien. ServiceNow permet de restreindre le compte par ACL et par table, ce qui est le bon endroit pour le faire : le mot de passe côté Vigicap ne porte aucune portée.
Taken from the vendor's own role model, and checked before publication.
02
What to enter in Vigicap
- Username
- Passwordsecret
03
Per-client routing
These fields are filled in client by client: they say which account in the ticketing tool the ticket must land under. A wrong value does not fail the push — it succeeds against someone else, which is why Vigicap checks them the moment you type them.
- Company (sys_id)
The core_company record tickets are filed against for this client.
32 hex characters
- Caller (sys_id)optional
Optional, and the recommended way to attach the client: a sys_user record belonging to this client. ServiceNow derives the company from it, which attaches the ticket WITHOUT needing write access to « company ».
32 hex characters
- Tableoptional
Defaults to incident. Any table extending task works (e.g. sn_customerservice_case).
incident
04
What it does, and what it does not do
ReCyF objectives it pre-fills
This connector feeds no ReCyF objective, and that is not a gap: it does not measure a client's posture.
What goes out to the tool
This connector WRITES: it creates a ticket from an action in the plan.
What comes back
The state of an already-created ticket comes back: its status, its closing date, its last activity. A closed ticket becomes a PROPOSAL a consultant confirms — never an action closed of its own accord. An agency that closes its own ticket must not be able to mark its own homework in the document an auditor reads.
How Vigicap handles your credentials.
Verification
This connector has been run end to end against a real instance of the tool, not merely tested against a mock.