SecurePoint Visitor
An ITAR visitor management system that holds up in an audit
SecurePoint USA provides visitor check-in, sanctions and watch-list screening, adjudication, and badge issuance as a hosted subscription service for regulated facilities. Possible matches wait for a person, foreign nationals are escorted at ITAR sites, and no badge prints until the checks clear.
The product tour is filmed in a demo organization with fictional visitors.
- Screened at check-in
- Against OFAC, BIS, UN, EU and UK lists before the badge prints.
- Held for a person
- A possible match waits for a reviewer's recorded decision.
- Escorts on the badge
- Escort requirements print on the badge and stay with the visit.
- Per-site pricing
- Unlimited visitor screenings, with no per-screening fee.
Full visit lifecycle
From preregistration to proof.
Every phase of a visit runs through one workflow, and each step leaves a record in the append-only audit log.
- 1
Before the visit: preregistration and preparation
The host preregisters the visitor, the visit email carries an Add to calendar file, screening runs at preregistration, and the site security profile sets the NDA, briefing and ID requirements.
- 2
Arrival: ID capture, screening and badge control
Government ID capture and a badge photo, sanctions screening against OFAC, BIS, UN, EU and UK lists, and a badge held until screening clears and the required documents are complete. Possible matches wait for a reviewer's recorded decision.
- 3
During the visit: host coordination and escorts
Host Hub alerts the host on arrival, the badge shows the escort requirement, and escort records stay with the visit.
- 4
After the visit: checkout, reporting and retention
Checkout is timestamped, the after-visit report carries the full session, and the append-only audit log keeps the decision history. Screening and review records are kept for 10 years.
The agreement and briefing each visit needs.
The site security profile decides whether a visit needs an NDA, a safety briefing and ID capture. The NDA & Safety page sets which NDA and video each site and visit purpose gets. The visitor signs at the kiosk, at the desk or on their own phone, and the badge waits until everything required is on the visit.
Filmed in a demo organization with fictional visitors.
Read the transcript
Admins set one NDA and safety briefing for the whole organization, and add exceptions for a site or a visit purpose.
Before a change makes kiosks refuse visitors, or stops asking for a step, the page names the sites it affects.
Hosts can add them to an invite. The visitor acknowledges them while registering, or at check-in when the site requires them at every visit.
At sites that turn it on, visitors who list U.S. citizenship attest they're a U.S. person. Others acknowledge their visit may need an escort and more review.
At the kiosk, signing stays locked until the visitor reaches the end of the agreement, and the safety briefing comes next.
At the front desk, visitors can sign on their own phone or right at the desk, with a typed or drawn signature.
The signature is saved with the visit, along with the name they gave and the time, and staff can open a receipt.
And if a required step is missing, the front desk sees what's still needed before the badge can print.
SecurePoint Visitor. Screen visitors at check-in, and keep the decisions on record.
Holds wait for a person. Badges wait for the evidence.
The screens your front desk, reviewers and auditors use, captured from a demo organization.
A held visitor gets a recorded decision.
A possible match holds the visit. The reviewer marks it not a match, approves or denies access, and adds a reason, such as a date of birth mismatch or a verified U.S. person. The decision is saved with the visit.

When a check-in step is missing.
The visit record lists what is still owed before a badge: an NDA, a safety briefing, the front of the ID. Until those are on the visit and screening has cleared, the badge does not print.
Read the transcript
A badge is only available once the visitor is checked in and approved.
While a possible match is under review, the visitor is asked to see a staff member, and the badge stays unavailable.
Here, the visitor agreement and a photo of their ID are missing, so the badge is refused, and the desk sees what's still needed.
Once those steps are done, the badge is available.
SecurePoint Visitor. Screen visitors at check-in, and keep the decisions on record.
Every step lands in the audit log.
Check-in, screening, review decisions, badge issuance, host notifications and checkout are recorded in an append-only, hash-chained audit log that application users cannot edit or delete, with a verifier that checks the chain.

Six modules that run the visit.
Each module handles one job. Together they make a complete visitor management system with a record at every step.
- ID capture and badge controlCapture government-issued IDs at check-in and print badges with site restrictions and visual indicators. Badge records tie to the visit for audit.
- Host Hub and notificationsHosts get an alert when a visitor arrives and see visitor status, pending approvals and coordination tasks without touching the front-desk system.
- After-visit reportingA structured report after checkout with screening results, host assignments, badge records, timestamps and reviewer actions.
- Screening and reviewMulti-list sanctions screening against OFAC SDN, the BIS Entity List, UN, EU and UK lists. Possible matches route to a person for a recorded decision.
- Front desk workflowOne screen for check-in, photo capture, badge printing and screening decisions: clear, hold or deny.
- Audit logs and evidenceAn append-only, hash-chained audit log that application users cannot edit or delete, with a verifier that checks the chain. Exportable as evidence packs.
One record for every role.
- Front desk
- One screen for check-in, ID capture, badge printing and screening decisions.
- Security
- Live visitor status, badge control, escort coordination, and holds that wait for a reviewer.
- Compliance
- Append-only audit logs, after-visit reports, evidence packs and screening history for regulatory review.
- Hosts
- Preregister visitors, get arrival alerts, and handle coordination tasks from Host Hub.
- Operations
- Site-level settings and visitor reports for each site.
Technical data access boundaries.
ITAR requires tight control over who can access controlled technical data. Visitor badges and escort rules have to reflect those boundaries without stopping the lobby.
Access boundaries on badges.
Badge templates and visitor types configured by site help distinguish who can approach controlled work areas. Escort requirements and site-specific rules are enforced by your procedures and reflected in how visitors are badged.
SecurePoint USA is not a policy engine or legal opinion. It provides visitor screening, controls, and logging that support the export control workflows defined by your FSO and compliance team.


CMMC Level 2: visitor evidence, not certification.
Your contract and assessment scope decide which CMMC requirements apply. SecurePoint produces direct evidence for escorting visitors (PE.L2-3.10.3) and for visitor access logs (PE.L2-3.10.4), and supports others. It does not provide CMMC certification.
Foreign-person visits: escort, confirm, report.
Visitors attest U.S.-person status at check-in. At an ITAR site, a foreign national needs an escort and host verification, and the desk can't admit them until an escort is assigned. After the visit, the host answers the after-visit questions and the report joins the record.
Filmed in a demo organization with fictional visitors.
Read the transcript
When the site requires it, a visitor who lists another country of citizenship acknowledges they're a foreign national, and that the visit may need an escort and more review.
The kiosk asks the visitor to wait for their host. The host gets an email asking them to come to the kiosk, check the visitor's photo ID, and print the badge. It also says the visit needs an escort.
At the kiosk, the host enters their name and confirms three things: they checked the visitor's nationality on their ID, they'll escort them at all times, and they won't share export-controlled technical data without authorization. Then the kiosk prints the badge.
When the visitor checks out, the host is asked for an after-visit report: whether any controlled technical data was shared, and a short summary. If it's late, reminders follow.
SecurePoint Visitor. Screen visitors at check-in, and keep the decisions on record.
Frequently asked questions
- What is an ITAR visitor management system?
- An ITAR visitor management system is a full-lifecycle platform that manages preregistration, ID capture, sanctions screening, host coordination, badge control, and audit evidence from an append-only log for facilities handling controlled technical data.
- Do I need to screen visitors under ITAR?
- Organizations handling controlled technical data should apply visitor screening and access controls to support documented approvals and export compliance reviews.
- What is a deemed export in the context of visitor access?
- A deemed export occurs when controlled technical data or technology is released or otherwise transferred to a foreign person in the United States. Visitor access to areas containing ITAR-controlled information can trigger deemed export considerations, which is why foreign national identification and access controls are part of ITAR visitor workflows.
- How does SecurePoint help FSOs manage visitor access?
- SecurePoint gives FSOs foreign national screening at check-in, visitor badges with site-configured indicators, escort workflow support, and append-only audit logs. FSOs can review visitor history across sites and export evidence packs for ITAR reviews without rebuilding spreadsheets.
- How does sanctions screening work at check-in?
- Screening runs when a visitor registers, or at the kiosk for walk-ins, against named sanctions and watch lists including OFAC, BIS, UN, EU, and UK lists. A possible match holds the visit for a reviewer, whose decision and reason are recorded with a timestamp. Each list refreshes on its own schedule.
- What happens after a visitor checks out?
- SecurePoint Visitor generates after-visit reports with complete session evidence: check-in and checkout timestamps, screening results, host assignments, badge records, and reviewer actions, all retained as append-only audit logs.
- How does SecurePoint Visitor handle host notifications?
- Host Hub alerts the host when a visitor arrives, shows the visitor's status, and supports coordination workflows including escort assignments and visit approval.
- How much does an ITAR visitor management system cost?
- Costs vary by vendor. SecurePoint USA positions visitor pricing as fixed per-site pricing rather than a per-screening fee model, which gives defense teams a clearer starting point for budgeting.
Related reading
See a full visit, start to finish.
Walk through preregistration, check-in, a held match, host coordination and the after-visit report with your team. Setup is guided: site configuration, front-desk training and kiosk deployment support.