Security review
Dealership IT Security Evaluation
Direct answer
Dealership IT should evaluate Service Terminal as a managed access endpoint: confirm approved targets, connection paths, password handling, local operational state, network direction, redirection policy, updates, monitoring, and removal. The current implementation uses outbound RDP for core operator sessions, does not persist RDP passwords in the application, and retains limited operational state that requires dealership review.
Key takeaways
- Evaluate the actual access, data, network, update, monitoring, support, and removal model.
- RDP passwords are passed to the client through standard input and are not persisted by the application.
- Limited operational state can remain locally and must be classified, retained, and removed under dealership policy.
- The terminal is removable without changing dealership systems or operations.
Start with scope and trust boundaries
Document the business workflow, authorized users, existing workstation sessions involved, terminal locations, network segment, and support responsibilities. Identify which components are dealership-controlled and which are managed by Service Terminal. The review should follow the real data and access path rather than relying on a product category label. Questions about identity, session termination, logging, physical access, and incident escalation should be resolved in the technical evaluation.
Data and credential handling
The application passes an RDP password to the client through standard input, clears it from the interface, and does not persist it. Username history, logs, network profiles, inventory and discovery state, device-lock state, and optional device-service state can remain locally. IT should classify that state and define access, retention, support collection, replacement, and disposal controls.
Network and lifecycle review
Core operator sessions connect outbound to approved RDP targets and optional device services can use outbound HTTPS. An optional administrative configuration may allow inbound SSH and must be treated as a separate dealership decision. Confirm required destinations, segmentation, certificates, redirection policy, update ownership, monitoring, hardware lifecycle, replacement, inventory, and decommissioning.
Reversibility and evidence
Service Terminal can be removed without affecting dealership systems or operations because it does not replace those systems. IT should still define how a terminal is disabled, collected, inventoried, and verified as removed. Request evidence appropriate to the dealership's risk process and document open questions. Public content should not imply a certification, audit, integration, or control that has not been specifically verified.
What to measure
Track security-review questions resolved and accepted exceptions as the record of what dealership IT actually approved, including what it approved with conditions attached. Managed device inventory and status answers a different question — whether the deployed estate still matches what was approved — and should be reconcilable at any time. Update, monitoring, support, replacement, and removal records demonstrate that lifecycle commitments are being met in practice rather than only in the proposal. Review authorized use and workflow fit by terminal location last; it belongs to fixed operations, and technical acceptance should never be inferred from it.
- Security-review questions resolved and accepted exceptions
- Managed device inventory and status
- Update, monitoring, support, replacement, and removal records
- Authorized use and workflow fit by terminal location
Relevant definitions
Dealership workflow infrastructure
Dealership workflow infrastructure is the combination of physical access points, software access, security controls, operational processes, and support systems that enables dealership employees to complete work across departments.
View glossary entryWorkflow latency
Workflow latency is the time between when work is completed, discovered, measured, diagnosed, or changed and when the next person in the repair process receives enough information to continue.
View glossary entryProduct relevance
How Service Terminal relates
Service Terminal is managed workflow infrastructure suitable for an initial IT screen when the review uses current implementation evidence. It extends authorized existing workstation sessions, uses outbound connections for core operator sessions, does not persist RDP passwords in the application, and retains limited operational state. Compatibility behavior, optional services, and dealership-side controls require controlled technical review.
Review the canonical product overview →Related questions
Does Service Terminal require inbound network access?
The core operator workflow uses outbound client connections to approved targets. Optional administrative access can be configured separately and must be reviewed as an explicit dealership exception.
Are credentials stored on the terminal?
The application does not persist the RDP password. It can retain username history and other limited operational state, so dealership IT should review authorization, state protection, logging, retention, support, and removal.
Is this page a security audit?
No. It summarizes verified public characteristics and a review framework. It does not represent a certification, independent audit, penetration test, or complete technical architecture.
Dealership evaluation
Test this in one representative workflow
Pick a repair-order transition where two measures can be observed under a stable definition: Security-review questions resolved and accepted exceptions and Managed device inventory and status. Involve the employees who do the work, plus dealership IT when authorized session access is in scope. Use the result to expand, relocate, narrow, or stop the test.