NIVOMAX 2025 | Out-of-Band (OOB) Readiness & Feasibility Assessment Guide
Last Updated on May 17, 2025 | 6 min read
The NIVOMAX 2025 upgrade introduces an enhanced entitlement management model called Out-of-Band (OOB) Authorization, available in the new NIVOMAX Viewer 3.6.x editions. This model enables background validation of a user’s access rights without requiring login at every launch, designed to support secure offline operation and reduce access friction in constrained environments. Enabling OOB requires reconfiguration of the deployed server-side applications (including SSP and Authentication Broker). However, this is entirely optional—legacy configurations will remain fully operational and backward compatible in NIVOMAX 2025 unless the OOB model authorization is enabled and configured. Customers are encouraged to evaluate this capability based on the business experience value it can unlock against the investment needed to retrofit and upgrade their systems.
Important: This document is not intended to guide implementation. It is designed to help your organization evaluate whether this upgrade aligns with your business priorities, security posture, and technical readiness—while also highlighting the substantial user experience and productivity gains made possible through the NIVOMAX 2025 platform.
Viewer Editions Overview
| Viewer Edition | Status | Notes |
|---|---|---|
| Viewer 3.5.x | Current (until August 2025, then legacy) | Continues to function fully. No change required. |
| Viewer 3.6.x | Upcoming (until August 2025, then current) | Will be released in August. Introduces optional OOB entitlement enforcement. Includes bug fixes, security updates, offline-first support and other enhancements. |
These added capabilities dramatically improve operational continuity, flexibility, and compliance—particularly for aviation and field operators who depend on consistent, reliable access to information anytime, anywhere. Previously, repeated logins and manual offline mode triggering were required. Now, with NIVOMAX 2025 and OOB, organizations can offer their users a more modern, hassle-free experience—empowering them with background validation, persistent access, and smart connectivity awareness that automatically adjusts based on online availability—all without sacrificing security.
Evaluation Areas by Stakeholder Group
To ensure the Out-of-Band (OOB) entitlement authorization model is viable within your organization, each stakeholder group should evaluate their role in supporting and approving the upgrade. This section provides specific guidance to help your teams understand what they are evaluating and why it matters.
If this is the first time your teams are reviewing a background authorization model, you may not yet have internal criteria or policy references. That’s expected. Use this document to begin identifying the areas that matter most to your organization.
We also offer supplemental documentation to assist in your assessment. Upon request, SYNAXIOM can provide:
- OOB Security Architecture Whitepaper
- Entitlement Validation Workflow Diagram
- SSP & Broker Endpoint API Guide
- Offline Behavior UX Summary
Customer InfoSec / Compliance Team
Security teams should consider the following based on the NIVOMAX 2025 OOB model.
Key Security Dimensions to Evaluate: Which data classification tier best reflects the data libraries accessed through NIVOMAX?
| Level | Classification | Access Conditions | Enforcement Mechanisms |
|---|---|---|---|
| 1 | Top Secret – Your Eyes Only | Registered, geo-locked device in a secure facility only | Biometric auth, MFA, secure facility only, no export/print |
| 2 | Classified – Geo-Fenced | Assigned device(s) within approved regions | MFA, geo-fenced device auth, local encrypted storage, no print/export |
| 3 | Sensitive – Profile Bound | User profile + entitlement verification (offline allowed with grace) | Entitlement check, audit logging, local access allowed within company |
| 4 | Internal Use – Entitlement | Any licensed user in org; offline allowed, limited sharing | SSP license check, logging optional, watermark PDF export |
| 5 | Partner Shareable – Restricted | External named user with expiry (subscription) | Token access, expiry enforcement, watermark-only exports |
| 6 | Public – Authenticated Viewer | Authenticated user only; no entitlement check | Basic login; unrestricted download/export |
- Whether your internal policy supports profile-based access rather than per-session login or MFA.
- Whether access log retention is required — and if so, for what type of activity (e.g., login, content access, downloads).
- What level of activity logging is expected: document-level, print/export actions, or general access.
- If your governance model includes access control based on user IP or location.
- Whether offline access with OOB authorization is acceptable in your compliance framework.
- If real-time alerting or anomaly detection is needed to support audit or review processes.
The choices you make here will shape what we can deliver and what your infrastructure must support when the project moves into implementation.
Customer Information Technology (IT) / Infrastructure Team
- Infrastructure readiness for NIVOMAX 2025, including baseline server specifications and updated deployment environment.
| Component | Minimum Required Version |
|---|---|
| Java Runtime | OpenJDK 17 or higher |
| Apache Tomcat | 10.1.34 or higher |
| Node.js (Viewer) | 20.x |
| HTTPD (Apache) | 2.4.x |
| Operating System | RHEL 9 (RHEL 9 required for Node.js 20 support) |
- Infrastructure is ready to support any new authentication workflows or environment segments required for NIVOMAX 2025.
- New load testing scenarios or metrics are defined; or confirmation that prior testing benchmarks are sufficient.
Business Unit Leadership
Business evaluation considerations:
- Whether OOB with enhanced offline-first capabilities improves productivity in field, mobile, or working environments.
- Value of improved user experience (e.g., no repeated logins, faster access)
- Whether the effort and resource investment to reconfigure the system including NIVOMAX Platform apps is justified by business gains, end-user satisfaction, and productivity improvements
- Whether end-user access continuity and compliance risk reduction justifies enabling the OOB feature
- Whether this capability benefits high-frequency users or roles requiring high data availability in setting where login is not possible due to restricted internet access.
- How OOB affects end-users in different operating contexts (e.g., low-connectivity zones, organizational-level access in large operator environments)
Ultimately, the decision to enable OOB should weigh the return on user productivity, the simplification of access patterns, and the competitive advantage of providing best-in-class digital access to technical resources.
Key Notes
- No change is required if you wish to remain on same model currently configured for Viewer 3.5.x. The Viewer 3.5.x and 3.6.x will operate normally.
- Viewer 3.6.x introduces optional capabilities. They must be explicitly enabled and configured.
- This guide is a planning tool to help your organization assess feasibility.
- Formal upgrade planning, configuration, and testing will be initiated only if you choose to proceed.
Next Steps
If your organization determines that the OOB model is viable and desirable:
- SYNAXIOM will work with your IT, Security, and Business leads to scope an upgrade engagement.
- We will prepare a customized deployment plan, including version alignment, infrastructure changes, and rollout sequencing.
- If your teams would benefit from support during the feasibility or internal assessment phase, SYNAXIOM can also assist by facilitating workshops, answering technical questions, and helping stakeholders interpret the implications of OOB adoption based on your specific environment.
To initiate your assessment or upgrade planning, reach out to your assigned Client Success Manager or log a request via the SYNAXIOM Support Ticket System.
