NOWISOR
Sign InGet Started

Access & Data Handling

Last updated: September 2026

We ask security teams to point Nowisor at their ServiceNow estate, so we owe you a precise account of what touches your data and what does not. This page is that account. Where it matters, we lead with the option that keeps your data in your hands. Every statement here describes something in the code rather than something in a policy, and where the two would differ we say what the code does.

Who we are, and where your data is processed

Nowisor SASU, Nice, France. The application and its database run in an EU region in the Netherlands (Railway europe-west4), with the database on a persistent volume in the same region.

Customer instance data — your scan findings and the configuration values behind them — is routed to our EU inference path by default, on every plan including the free one: an EU-hosted gateway in Frankfurt with the model pinned to an EU cloud region, under a signed GDPR Article 28 DPA. Internal work that touches no customer instance data, such as knowledge-base drafting, uses a US-hosted provider instead. Connected accounts and above can make a different, explicit choice — Enhanced data protection sends inference to a separate, dedicated Anthropic workspace key rather than the shared one, processed in the US — and an explicit choice is never silently upgraded to something else.

On that EU option we have switched prompt and output logging off at the gateway, so under that DPA it keeps no copy of the request or the response. The model behind it is served by AWS Bedrock in Frankfurt under its own terms, which makes this EU-resident processing with no gateway-side logging rather than end-to-end zero retention. Retention and model-training terms for both are set by our agreements with those providers, not by a setting in this product. What the product itself guarantees is narrower and testable: a request the selected option cannot serve is refused and the credit refunded — it is never re-routed to the standard endpoint.

If your organisation has a specific data-residency requirement (for example, EU-only processing for NIS2 or DORA), contact us before connecting an instance so we can confirm the right option for your case.

Who else is involved

The list below is not a policy statement — it is the outbound allow-list the application enforces at runtime. A destination that is not on it is refused before a network connection is opened, so a vendor cannot quietly join this list without appearing here.

Involved in handling your data

  • Anthropic (api.anthropic.com) — model inference for advisor answers.
  • Requesty (router.eu.requesty.ai) — our EU inference gateway, Frankfurt.
  • AWS — Bedrock in eu-central-1, behind that gateway. A sub-processor of Requesty rather than a vendor we call directly.
  • Stripe (api.stripe.com) — subscription billing and VAT details.
  • Resend (api.resend.com) — verification and password-reset email.
  • OpenAI (api.openai.com) — an alternative model provider the application can be configured to use instead of the above. It carries no residency terms, which is why it is not the default.
  • Your own ServiceNow instance — allowed by hostname class (*.service-now.com, *.servicenow.com), HTTPS only.

Security intelligence sources, which receive nothing of yours

These are read, never written to: api.github.com, api.vulncheck.com, api.first.org, www.cisa.gov, services.nvd.nist.gov and cveawg.mitre.org. They supply advisory and exploitation intelligence. No customer identifier, instance name or finding is ever sent to any of them.

The list is what this deployment is configured to allow, and an operator can add a host to it — doing so is announced in the application log when the guard starts, so it is never a silent change. We would rather describe a list that can change than imply one that cannot.

There are no analytics, tag managers or third-party scripts on this site. The only scripts the pages load are our own, and typefaces are served from our own domain.

The outbound boundary

Every outbound call the application makes is checked against that allow-list on protocol and hostname before a socket is opened, and a refused destination raises an error and records a security event rather than failing quietly. The guard is installed during boot and a failed install stops the process, so there is no window in which it is not running. Any destination that is not loopback must be HTTPS, and redirects are followed by the guard itself rather than delegated, with the authorization header dropped whenever a redirect changes host.

What we cannot offer is a fixed set of source IP addresses. Our platform provides no network-level egress control, so if your instance requires inbound IP allow-listing, the upload path below is the route that works today. We would rather say so than publish a range we cannot hold to.

The paste-driven option: your logs never leave your tenant

Our forensic checks — such as the CVE exposure check — run from a read-only Background Script you run yourself on your instance. You paste its output into the page. For our free checks the verdict is computed in your browser: the pasted log text is never transmitted to us. The detection scripts only read log tables and print a result — they cannot write to, change, or call out from your instance. If you need to generate a dated PDF, only the computed verdict (the conclusion) is sent to render it — never the underlying log lines — and the anonymous path stores nothing.

Two ways in: connected or upload

QuestionConnectedUpload
What we readYour instance, over its own REST Table API, with a per-table field allow-listA results file produced by our open-source bundle script, run by your team inside the instance: the reads a connected scan makes, and no others
What crosses the networkRead calls inbound to your instance. Our outbound calls are allow-listed by hostname before a socket is opened; source-IP allow-listing is not available todayOne file, outbound, that you review before sending
Credentials we holdEncrypted AES-256-GCM under a key kept separate from the session secret. They are deleted when you disconnectNone
Installed in your instanceNothingA scoped application you install through your own change process, or our five standalone Background Scripts for a reduced review. Both are open source
What it producesPosture Map, Remediation Leverage, Evidence Table, scheduled scans and driftThe same Posture Map, Remediation Leverage, Evidence Table and reports, as of the capture date. Re-upload on your own cadence
PlanConnected and aboveConnected and above; the basis of Self-Hosted Assurance
Best forCloud instances that need posture to stay currentSelf-hosted, egress-locked or sovereign instances

What runs inside your instance, if you choose the upload route

Nothing reaches inward on this route and no credential leaves your side, but something does go in, and it goes in the normal way: a scoped application you install through your own change process, or our five standalone Background Scripts for a reduced review. Both are open source under Apache-2.0, so your reviewer reads the same code we do.

The mechanism, precisely, because it decides who has to be in the room: the application is built and installed with the ServiceNow Fluent SDK, which needs Node and the SDK on the machine doing the install. It is not a plain update-set XML import, and there is no SDK-free install path today. The five Background Scripts need none of that — they are pasted and run — which is why they exist as the lighter option.

What a connected scan reads

A connected scan reads 89 tables over your instance's own REST Table API, and every call carries an explicit field list — we ask for the columns a check needs and no others. It does not modify your instance as part of scanning.

Platform configuration. sys_properties, sys_rate_limit_rules, sn_vsc_instance_hardening_settings — configuration property values (password-type and secret-shaped values are replaced by a marker at the read), rate-limit rules, and your Security Center hardening settings.

Access control. sys_security_acl, sys_security_acl_role, sys_user, sys_user_has_role, syslog_transaction — ACL rules with their conditions, the roles gating them, and which account holds which role — and, for each admin account marked web-service-only, how many transactions it made in the last 90 days (syslog_transaction: a count, never a transaction's contents or URL), because such an account never logs in interactively.

Data model. sys_db_object, sys_dictionary — which tables and fields exist, so a check never runs against something your instance does not have.

Server-side code. sys_script, sys_script_include, sysauto_script — business rules by count, Script Includes by name and access level, and scheduled jobs.

Web services. sys_ws_definition, sys_ws_operation — Scripted REST definitions and their operations, for authentication and ACL posture.

Non-human identities and integrations. oauth_entity, oauth_credential, discovery_credentials, ecc_agent — OAuth clients and when each last issued a token, credential records by name and type, and MID Servers.

Applications and plugins. sys_plugins, v_plugin, sys_store_app, sys_scope, sys_upgrade_history — which plugins, Store applications and application scopes are installed and active, so a finding can say whether a feature is even present — and the upgrade history of the instance (sys_upgrade_history: read where the connection permits; best-effort), so a record can be told apart from what an upgrade delivered.

AI agents. alm_ai_digital_asset, auth_server_connection, auth_server_connection_tool_scan_job, auth_server_connection_tool_scan_result, mcp_auth_scopes, np$sys_generative_ai_model_config, oauth_entity_scope, sn_ai_governance_ai_asset_virtual, sn_ai_governance_ai_configurations_virtual, sn_ai_governance_asset_metadata_fields, sn_ai_governance_asset_metadata_staging, sn_ai_governance_asset_semantic_tag, sn_ai_governance_asset_state_lifecycle_mapping, sn_ai_governance_enrichment_field_strategy_m2m, sn_ai_governance_enrichment_recommendation, sn_ai_governance_enrichment_strategy, sn_ai_governance_enrichment_target_field, sn_ai_governance_enrichment_task, sn_ai_governance_m2m_asset_detail_semantic_tag, sn_ai_governance_reconcile_duplicate_task, sn_ai_governance_reconcile_duplicate_task_detail, sn_ai_governance_st_related_variants, sn_ai_sp_asset_security_task, sn_ai_sp_threat_analysis_config, sn_aia_agent, sn_aia_agent_config, sn_aia_agent_tool_m2m, sn_aia_external_agent_configuration, sn_aia_external_agent_provider, sn_aia_team, sn_aia_team_member, sn_aia_tool, sn_aia_trigger_configuration, sn_aia_usecase, sn_awh_mcp_client_integration, sn_awh_mcp_otel_gaic_log, sn_awh_mcp_policy, sn_awh_mcp_policy_attributes, sn_awh_mcp_policy_mapping, sn_awh_mcp_policy_type, sn_awh_st_mcp_tools_view, sn_mcp_server, sn_mcp_server_registry, sn_mcp_server_tool, sn_mcp_server_tool_definition_assoc, sn_mcp_tool_definition, st_awh_mcp_otel_mcp_servers, st_awh_mcp_otel_mcp_tools, sys_agent_access_permission_set_configuration, sys_agent_access_role_configuration, sys_agent_access_role_mapping — AI agent definitions with their role and instruction text, read as-is like ACL scripts; tool definitions by name, type and target table (no script text); the tools each agent uses and the inputs it passes them (secret-shaped values are replaced by a marker at the read); teams, use cases and their triggers; the MCP servers this instance runs and the tools they expose, the external MCP servers and agent providers it connects to; which AI and machine identities exist, by user name, and which of them hold admin or security_admin; two AI agent properties by name and value; the AI threat-analysis settings, as whether each is active and its sample size; a count of open AI security tasks; and a row count, nothing more, of the AI tables the Table API does not serve (a connection is refused them, an upload counts them). The AI-surface checks are scored from these reads.

Compensating controls. ip_access, sys_api_access_policy, oauth_entity_auth_scope_mapping, sys_user_role — whether IP address access control, REST API access policies, Explicit Roles and OAuth client Auth Scopes are in place — as counts and flags (read with reader app 1.3.4, beside the verdict and never inside it). No address range, policy name or user name is read into a report.

Native scanner (Security Center). scan_result, scan_finding, scan_check_execution, scan_score, scan_check, sn_vsc_hardening_compliance_scores — what an Instance Scan you ran left behind, beside the verdict and never inside it: the native scans (number, state, type, finding count, duration and date); the check inventory by name, category, priority and whether each check is active — never a check's script field; and for the newest completed scan, which check each finding is for and whether it is muted, the checks it executed and its category scores. Also the Security Center hardening compliance score (sn_vsc_hardening_compliance_scores), which a stock instance does not serve to the Table API, so it is read by the scan pack inside the instance only. Nowisor never starts a scan.

Knowledge bases. kb_knowledge_base, kb_uc_can_read_mtom, user_criteria, sp_page — knowledge base read criteria, the roles a criterion names (whether the public role is among them) and whether the portal's knowledge pages are marked Public, for public-exposure checks. Article bodies are never fetched.

Three details matter more than the list, because they are the ones a reviewer should challenge. ACL condition scripts are read in full — that is how an over-permissive rule is proven rather than guessed at. Script Include bodies are not: they are matched by a query your instance evaluates, and only the names of matching records come back. And credential records are read by name, type and target only — never a secret value, which is not a column we ask for.

The product does not enforce a role at connect time; the account you connect decides what we can read. We publish the role we verified: x_nowisor_vsme.reader_recommended + access_analyzer_admin (recommended) or x_nowisor_vsme.reader (minimal); nowisor's roles come as a scoped application that installs read and query rights only. It never needs admin, security_admin, rest_api_explorer.

What the integration account needs is read access to the tables above; how your platform team grants that is their call, and the narrower the better.

Writing to your instance

The one write path is explicit and opt-in. Remediation ticketing is the only thing that writes to your instance: it creates a change request or incident when you click to confirm a server-built request you can see first, or when a scan schedule you set opted into automatic tickets, and it adds a work note to, or closes, a ticket it created when a later scan no longer detects the finding, if that schedule opted into it. Nothing is written silently, and no other record is ever modified or deleted.

We do not write to your instance except the remediation-ticket path above.

Credentials, retention and deletion

  • Credentials are encrypted at rest. OAuth tokens are encrypted with AES-256-GCM before storage, under a key kept separate from the session secret. With OAuth we never receive your ServiceNow username or password. If you connect with basic auth instead, that username and password are stored encrypted the same way and sent only to your instance.
  • Account passwords are hashed with scrypt; we never store plaintext passwords.
  • You can disconnect at any time, which removes the stored connection and its tokens; the scan history, triage decisions and tickets stay with your account until the account is deleted.
  • Full scan detail is kept for the 3 most recent scans of each instance and for any scan in which an open finding was detected. Older scans keep their summary (score, band and finding counts) and lose the detail.
  • Thirty days after an account ends (a free plan with no subscription and no managed engagement), all instance data is deleted: connections and their credentials, scan schedules, snapshots and scan history, triage decisions and tickets. The deletion is recorded in our audit log. The account and login remain; reconnecting afterwards requires authorising again.

Trust artifacts

We are a small, focused vendor and we hold no third-party security attestation today. Rather than name a scheme we have not completed, this page states what the code enforces and points at where each control lives, so your reviewer can test the claims instead of taking them. If your procurement process needs one of these to proceed, tell us — and in the meantime, the paste-driven path above lets you get value without connecting anything at all.

Related

How a finding becomes a verdict, what it is compared against, and when it withdraws itself are a different subject with its own page: how verdicts are computed.

Plans and billing

What ServiceNow access do I need to connect?

A read-only integration. You authorize Nowisor with an account that has read access to the tables we audit (ACLs, REST definitions, system properties, roles, scheduled jobs, audit configuration) via OAuth or scoped credentials — no admin or write access required. The only write Nowisor ever makes is an explicit remediation ticket you confirm per action, on Managed engagements.

Is there a free trial on paid plans?

Yes — the monthly self-serve plans (Practitioner and Practice) include a 14-day trial. You add a card at checkout and aren't charged until the trial ends; cancel anytime before then and you pay nothing. Connected is invoiced annually and has no trial.

Are there usage limits?

Paid plans aren't metered by question — the advisor is unmetered on every paid plan. Recon (free) includes 25 credits for its lifetime: each chat answer or code review uses one.

How many instances can I connect?

Plans below Connected connect none — they run in your tenant or from pasted output. Connected connects 1 production instance. Multi-instance estates are a managed engagement. Limits are enforced server-side.

Where is my data stored?

Account data, conversation history, and instance snapshots are stored and processed on EU infrastructure (our hosting runs in an EU region), encrypted in transit, with ServiceNow OAuth tokens encrypted at rest (AES-256-GCM). We don't sell your data or use it for advertising. Answer generation that carries anything from your instance is routed to our EU inference path by default, on every plan — see “Does my ServiceNow data get sent to the AI model?” in the homepage FAQ.

Does my ServiceNow data get sent to the AI model?

Yes — to answer you, your query plus relevant context (knowledge-base articles and, if you've connected an instance, your scan findings and configuration values such as hardening property settings) is sent to our AI provider (Anthropic's Claude or OpenAI) over an encrypted API. We never send passwords, API keys, or OAuth tokens. By default, anything carrying instance data is routed to our EU inference path rather than to the shared US endpoint, and that routing is enforced in code. Connected accounts and above can enable Enhanced data protection (requests go to a separate, dedicated Anthropic workspace key rather than the shared one, processed in the US), or EU data residency, which routes inference through an EU-hosted gateway to Claude models pinned to EU regions (Frankfurt) under a GDPR Art. 28 DPA. On that EU option we have switched prompt and output logging off at the gateway, so under that same DPA it keeps no copy of either. The model behind it is served by AWS Bedrock in eu-central-1 (Frankfurt) under its own terms, which makes this EU-resident processing with no gateway-side logging rather than end-to-end zero retention. Retention and model-training terms for those two options come from our agreements with those providers rather than a setting in the product; what the product enforces is that a request the selected option cannot serve is refused and the credit refunded, never re-routed to the standard endpoint. If your policy prohibits sending configuration data to a third-party model, the open-source detection scripts (Recon) run entirely on your side with nothing leaving your instance.

Can I switch or cancel later?

Yes. Monthly self-serve plans switch or cancel anytime from the billing portal. Connected is an annual invoice (€34,800) and renews yearly.

Can consulting teams use Nowisor for client engagements?

Yes — that's the Practice tier: the in-tenant scan pack and Active Risk correlation across client engagements, from pasted output, with no connection to a client instance. A year of Practice costs less than one billable engagement.

What is the Active Risk Report?

Included from Practice: it pairs each scan finding with ~7 days of runtime activity from your instance (audit, event, and transaction logs) and marks it EXERCISED, DORMANT, NOISE, or INVESTIGATE — so you can tell an actually-exploited endpoint from a misconfigured-but-untouched one, and qualify every deferral by the log coverage available.

Contact

Questions about data handling, a security questionnaire, or a residency requirement? Reach us via the main site and we will respond directly.

Terms of Use/Privacy Policy/How verdicts are computed

© 2026 Nowisor SASU · Nice, France · EU data processing

PricingKnowledge BaseBlogCVE CheckAI CheckFAQ