INDAG · For IT departments

What your IT team needs to know about INDAG.

INDAG is a Windows desktop application for background investigations and employment processing. It runs on your agency's computers and keeps every applicant record on your agency's own shared drive. Porter Nexus Technologies never connects into your network and never receives applicant data.

Applicant dataYour shared folders only
Inbound connectionsNone
OutboundHTTPS to updates.porternexustech.com, optional
DeploymentMSI, Intune, ConfigMgr, PDQ or GPO

Where data lives

Applicant records, memos, employment files and uploaded documents are stored only in the shared folders your agency sets up. Program updates and uninstalling INDAG never touch INDAG's data folders.

WhatWhere
Applicant records, memos, employment files, uploadsYour agency's shared folders, for example \\fs01\INDAG\Memos and \\fs01\INDAG\Assignments
Program files, machine-wide install%ProgramFiles%\PorterNexus.INDAG
Program files, per-user install%LocalAppData%\PorterNexus.INDAG
INDAG data on each computer (encrypted caches, offline saves, backups)%AppData%\INDAG.7, %LocalAppData%\INDAG.7
Install kit settings%ProgramData%\Porter Nexus\INDAG (staff: read only)
IT policyHKLM\SOFTWARE\Policies\Porter Nexus\INDAG
Agency license<shared assignment folder>\indag-license.json, plus a copy on each computer for offline use

Network traffic

Nothing connects into your network from Porter Nexus. INDAG's only internet traffic is outbound HTTPS to updates.porternexustech.com, and only for the purposes below. Plain http:// sources are refused.

PurposeWhenWhat INDAG sends
License check20 seconds after start, then every 12 hoursAgency key, a random installation ID, INDAG version, update channel and profile role. No names and no records.
Online updatesEvery few hours, only when UpdateMode is OnlineAgency key, version and channel. Downloads program files only.
Agency packWhen a manager chooses to download itAgency key. Downloads your signed agency settings, forms and letterhead.
Crash reportsOff unless you turn them onINDAG version, Windows version, profile role, error type names and program locations. Messages, file paths, line numbers and anything typed into INDAG are removed before sending.

Allow updates.porternexustech.com over HTTPS through your web filter if INDAG will check its license or updates online. Networks with no internet access are covered under Licensing and offline networks.

Installing INDAG

Porter Nexus emails your IT contact a private install kit link. The link expires 14 days after it is sent, and the kit page shows Porter Nexus when it was opened. Don't forward it outside your IT team.

Kit fileWhat it is
PorterNexus.INDAG-….msiMachine-wide installer (Program Files, needs administrator)
PorterNexus.INDAG-…Setup.exePer-user installer (user profile, no administrator needed)
INDAG-provisioning.jsonYour agency name, agency key, update channel and first license. Treat it like a password.
*.indagpackYour agency pack (names, questionnaire forms, letterhead), signed by Porter Nexus
Deploy-INDAG.ps1Installs and configures INDAG (PowerShell 5.1 or 7)
PorterNexusINDAG.admx and .admlGroup Policy templates for the same settings
Approve-INDAGUpdate.ps1Optional: download, scan and approve each release before your computers get it

Before you start

  1. Create the agency's INDAG shared folders. INDAG staff need read and write access.
  2. Decide how INDAG gets updates (see Updates).
  3. Allow updates.porternexustech.com if INDAG will go online.

Machine-wide (recommended for managed computers)

Run as administrator on each computer, or through Intune, ConfigMgr, PDQ or a GPO startup script:

.\Deploy-INDAG.ps1 -SharedMemoFolder "\\fs01\INDAG\Memos" -SharedAssignmentFolder "\\fs01\INDAG\Assignments"

This installs the MSI, saves the provisioning file and agency pack to %ProgramData%\Porter Nexus\INDAG, and sets the shared folders and update policy under HKLM\SOFTWARE\Policies\Porter Nexus\INDAG. Exit code 0 means success. Logs: %TEMP%\INDAG-deploy.log and %TEMP%\INDAG-msi.log. Staff then open INDAG with no setup questions, apart from the workspace passphrase once per computer if your workspace uses one.

Per user

  1. Once per computer, as administrator: .\Deploy-INDAG.ps1 -Mode Settings -SharedMemoFolder … -SharedAssignmentFolder … -UpdateMode Online (or -UpdateMode Approved -ApprovedFolder "\\fs01\INDAG\Releases").
  2. For each user, in that user's context: .\Deploy-INDAG.ps1 -Mode PerUser. This runs the setup file silently.

Group Policy and Intune values

All values are strings under HKLM\SOFTWARE\Policies\Porter Nexus\INDAG. Deploy-INDAG.ps1 sets them for you, or use the ADMX templates from the kit. Policy always wins over settings made inside INDAG.

ValueMeaning
SharedMemoFolderThe agency's shared memo folder
SharedAssignmentFolderThe agency's shared assignment folder
UpdateModeOff, Online or Approved. Anything else is treated as Off.
UpdateSourceFor Approved: the approved share or an internal https:// address. For Online: leave empty.
UpdateTokenFor Online: the agency key. Restrict who can read this policy.
UpdateChannelstable (default) or pilot
CrashReportsOn sends crash reports. Off or not set never sends them.

What INDAG managers can't change

On any computer IT manages (a machine-wide install, any value under the policy key, or kit settings in %ProgramData%), INDAG managers can see but not change the update choice, approved-updates folder, channel, agency key or crash reports. Each of those settings shows "Managed by your IT department." Managers still manage INDAG users, the workspace passphrase, agency settings, agency packs and license import.

Updates

A machine-wide install never updates itself. When Porter Nexus announces a release, you deploy the new MSI the same way you installed the first one. The three update modes below apply to per-user installs.

UpdateModeWhat happensGood for
OffINDAG never checks. IT installs new versions.Agencies with their own software deployment
ApprovedIT downloads each release, scans it, then approves it into a share that INDAG computers read. Computers install only approved releases.Agencies with EDR, change control or offline networks
OnlineINDAG downloads from updates.porternexustech.com with the agency key and installs when INDAG closes.Small agencies without a security team

Updates download in the background and install only after INDAG closes, never during a save. If a download fails (offline, proxy, revoked key), INDAG keeps working and tries again later. Releases go to the pilot channel first and to stable after they've been proven.

Approving each release yourself

  1. Create a share for approved releases, for example \\fs01\INDAG\Releases: staff read only, IT write.
  2. When a release is announced, on any admin PC run
    .\Approve-INDAGUpdate.ps1 -Action Fetch -HoldingFolder D:\INDAG\Holding
    It asks for the agency key, downloads the release and checks every file against the release list's SHA-256 hashes and the Porter Nexus signature. Nothing reaches INDAG computers yet.
  3. Scan the holding folder with your security tools.
  4. When it's cleared, run
    .\Approve-INDAGUpdate.ps1 -Action Approve -HoldingFolder D:\INDAG\Holding -ApprovedFolder "\\fs01\INDAG\Releases"
    It re-checks every hash, copies the packages, switches the release list last so computers never see a half-copied release, and records who approved what in approvals.log.

For offline networks, run the Fetch step on an internet-connected PC, carry the holding folder across, and run the Approve step inside.

Security software

INDAG updates with Velopack, an open-source updater for Windows applications. Like any self-updating program, it does things endpoint protection watches for: a setup file unpacks a program into the user profile, and the updater replaces program files. Here is how to handle that with SentinelOne, CrowdStrike, Defender for Endpoint and similar tools.

  • Allow by publisher, not by path or hash. Production releases are code-signed by Porter Nexus Technologies. Hashes change with every release, so hash rules break on each update. Current pilot builds are not yet signed while publisher signing is being set up.
  • Application control. If AppLocker, WDAC or your EDR blocks programs in user profiles, use the machine-wide install.
  • Defender ASR prevalence rule. "Block executable files unless they meet a prevalence, age or trusted list criterion" can block a brand-new release for its first days. Use the Approved mode or a publisher allow rule.
  • Inspect before deploying. Approved mode lets your scanners inspect every release before any computer installs it.

INDAG's installer does not add certificates to any Windows certificate store.

Files on the shared drive

Your antivirus can't scan files that INDAG encrypts, and a program rewriting encrypted files on a share can look like ransomware to EDR. So each INDAG workspace stores its shared-drive files in one of two formats, and an INDAG manager can switch between them.

FormatOn the shared driveOn each computer
Plain (default for new workspaces from INDAG 7.0.6)Ordinary files your antivirus can scan. Uploaded documents keep their own extension, for example .pdf. INDAG's settings files are readable text with a signature made from the workspace key, so a hand-edited file is refused.Encrypted (AES-256-GCM)
Encrypted by INDAG (workspaces created before 7.0.6)Employment records, uploaded documents and settings files encrypted with the workspace keyEncrypted (AES-256-GCM)

Memos and the assignment and investigator lists are plain on the shared drive in both formats. In the plain format, your drive permissions protect the files: limit the shared folders to staff your IT has cleared. If your CJIS policy requires criminal justice information on that drive to be encrypted at rest, keep the encrypted format or use encryption your IT manages for the drive.

An existing workspace keeps its format until a manager switches it in Team Settings → Security and sign-in → Files on the shared drive. Every computer must run 7.0.6 or later first. The switch backs up every file it changes before rewriting it, and an interrupted switch can be run again safely.

Sign-in and access

  • Licensed agencies sign in with their Windows accounts. INDAG managers add each person by name and send an invite code, which links that person to their Windows account.
  • Four roles: Investigator, Background Manager, Employment Specialist and Employment Manager. One person can hold more than one role. Permissions are enforced by INDAG's services as well as its screens.
  • A workspace can have a passphrase that protects the workspace key. Staff enter it once per computer. INDAG does not require Active Directory.

Licensing and offline networks

Each agency has one agency key, delivered in the install kit, used for the license check, agency packs, online updates and opt-in crash reports. Licenses are signed by Porter Nexus, and INDAG checks the signature, so a license file can't be edited. The kit includes a first license, so INDAG works immediately.

  • Offline grace. A license stays valid for the agency's grace period after it was issued: 30 days by default, up to 400 days for air-gapped agencies.
  • Networks without internet. Download indag-license.json from your agency's INDAG page before the confirm-by date shown in Team Settings → License, and have an INDAG manager import it there.
  • If a license ends or is suspended, INDAG becomes read-only. Records still open, print and export, but nothing new or edited is saved until the license is renewed. INDAG is never locked out of its own records.

CJIS considerations

Background files contain criminal justice information covered by the FBI CJIS Security Policy. INDAG is built so that information stays under your agency's control:

  • Porter Nexus does not store, receive or have network access to applicant records. Its servers hold only program files, signed licenses, agency packs and admin data.
  • Access control on the shared folders, encryption of the drive and audit of file access stay with your agency's existing controls.

Your agency's CJIS Systems Officer decides how INDAG fits your security policy. Porter Nexus can walk your IT and CJIS staff through any part of this page.

Common questions

Does INDAG need administrator rights?

The machine-wide MSI needs administrator rights to install. The per-user installer does not. Day-to-day use never needs administrator rights.

Can Porter Nexus push an update to our computers without us?

Only if you choose the Online mode for per-user installs. Machine-wide installs and the Off and Approved modes never install anything you haven't deployed or approved.

What happens if a computer loses its connection to the shared drive?

INDAG saves an encrypted copy on that computer and syncs it automatically when the drive comes back. If two people changed the same file, the competing version goes to a conflict queue instead of overwriting the other.

Does uninstalling INDAG delete records?

No. Records live on your shared drive, and uninstalling or updating INDAG never touches INDAG's data folders on each computer.

What if our agency key leaks?

Contact Porter Nexus. We revoke the key and issue a replacement. Revoking a key never removes or locks your records.

Who do we contact?

Use the contact details in your install kit email, or write to info@porternexustech.com.