Skip to content

FAQ & Troubleshooting

FAQ & Troubleshooting — SenseOps Writeback

Below are answers to common questions about SenseOps Writeback.

What is Writeback and where does it need to be installed?

General: What is Writeback and where does it need to be installed?

Answer:

SenseOps Writeback enables data write-back from Qlik to your data warehouse. It is installed on a dedicated Writeback server, such as your QLIK-GW server, and uses Node.js as its runtime.

What do we need to have ready before installation?

General: What do we need to have ready before installation?

Answer:

Before installing Writeback, ensure that the following prerequisites are met:

  • A SenseOps portal account created at senseops.com
  • Node.js installed on the Writeback server
  • The latest App Extensions and Writeback Installer packages downloaded from the SenseOps portal
  • Microsoft SQL Server host and port details confirmed, along with an account that has write permissions
  • An SSL certificate in .pfx format for the Writeback server
  • A firewall rule configured for the Writeback port (default: 4001)

Refer to Section 3 of the Writeback Architecture & Installation Guide for detailed installation prerequisites.

Can SenseOps provide documentation for an internal security review?

General: Can SenseOps provide documentation for an internal security review?

Answer:

Yes. On request, SenseOps can provide the dependency inventory, Architecture & Installation Guide, and additional technical or security documentation required for your internal review and approval. This can include documentation to support alignment with frameworks such as FFIEC and NCUA for regulated financial institutions.

Why does Writeback require Node.js?

Security: Why does Writeback require Node.js?

Answer:

Writeback uses Node.js as its runtime for handling write operations. As with other Node.js applications, security considerations include third-party npm packages, supply-chain risks, and unpatched dependencies.

Writeback addresses these considerations through version-pinned dependencies and a defined Node.js LTS patching process.

How does SenseOps manage third-party npm dependencies?

Security: How does SenseOps manage third-party npm dependencies?

Answer:

SenseOps provides an inventory of third-party npm libraries used by Writeback, including their exact versions. Your security team can use this inventory to scan dependencies with Snyk or an equivalent Software Composition Analysis (SCA) tool before approval.

Dependencies are version-pinned, and packages are not fetched or installed dynamically at runtime.

Is Writeback vulnerable to RCE, XSS, or SQL injection?

Security: Is Writeback vulnerable to RCE, XSS, or SQL injection?

Answer:

Writeback uses measures intended to address these security risks:

  • Remote Code Execution (RCE): Writeback does not execute user-supplied commands or expose shell or eval-style interfaces.
  • SQL Injection: Database interactions use parameterized queries rather than dynamically concatenating user input into SQL statements.
  • Cross-Site Scripting (XSS): User input is validated and sanitized at the API layer before being processed or stored.

How does Writeback handle authentication?

Security: How does Writeback handle authentication?

Answer:

Writeback authenticates through the existing Qlik security context. It does not maintain separate user credentials or issue its own long-lived authentication tokens. Access is governed by the identity and permissions model already configured in Qlik.

How is the Node.js runtime kept patched and secure?

Security: How is the Node.js runtime kept patched and secure?

Answer:

Writeback is certified against the current Node.js Long-Term Support (LTS) release. When Node.js publishes a security update, the SenseOps support process includes compatibility validation against that update.

This allows the Node.js runtime to be patched according to your maintenance schedule, subject to compatibility requirements.

What deployment and infrastructure security controls does Writeback support?

Security: What deployment and infrastructure security controls does Writeback support?

Answer:

SenseOps Writeback supports the following deployment and infrastructure controls:

Control Support
Service account Runs under a non-administrator service account.
Network exposure Uses a configurable port that can be restricted through firewall rules.
Encryption in transit Supports TLS 1.2/1.3 with trusted certificates.
Secrets management Secrets are encrypted; credentials are not stored in code or configuration files.
Logging Supports application and security logging.
Outbound access Does not require outbound internet access to operate.

Still Stuck?

Reach out to the SenseOps support team if you need further assistance with installation, configuration, or security-related questions.