Frequently Asked Questions
Everything you need to know about Sit(x), from general overview to technical details and security compliance.
General Questions
What is Sit(x)?
Sit(x) is a cloud-hosted situational awareness platform built by Booz Allen Hamilton. It provides a fully managed TAK server environment with real-time blue force tracking, secure messaging (GeoChat), mission management, data package distribution, and enterprise administration — all hosted on AWS GovCloud (US).
Who is Sit(x) designed for?
Sit(x) serves Department of Defense organizations, federal agencies, state and local government, law enforcement, fire departments, EMS, search and rescue teams, and any organization that needs real-time location awareness and secure team coordination using the TAK ecosystem.
How is Sit(x) different from running my own TAK Server?
Sit(x) eliminates all infrastructure management. You don't provision servers, manage certificates manually, patch operating systems, or build admin tools. Sit(x) adds web-based administration, multi-tenant organization isolation, enterprise federation, multi-factor authentication, comprehensive audit logging, and continuous software updates — all managed for you on AWS GovCloud.
What TAK clients does Sit(x) support?
Sit(x) works with all major TAK clients: ATAK (Android Team Awareness Kit), iTAK (iOS), WinTAK (Windows), and web-based interfaces. Any TAK client that supports standard Cursor on Target (CoT) protocols is compatible.
How quickly can my organization get started?
Organizations can be onboarded and operational within days. There is no hardware to procure, no software to install on servers, and no complex network configuration. The Sit(x) team provisions your organization, and users connect their TAK devices immediately.
Can I federate with other organizations on Sit(x)?
Yes. Sit(x) provides policy-controlled federation that allows selective data sharing between organizations. Federation channels are time-bound, scope-restricted, and fully audited. Both organizations must approve the federation before data sharing begins.
Does Sit(x) work offline or in disconnected environments?
Sit(x) is primarily a cloud-hosted service requiring internet connectivity. TAK clients (ATAK, iTAK, WinTAK) continue to function with cached map data and local peer-to-peer communication when connectivity is temporarily lost, and automatically sync when connectivity is restored.
Technical Questions
How does Sit(x) handle TLS certificates for TAK clients?
Sit(x) provides automated TLS certificate lifecycle management through the web admin dashboard. Administrators generate client certificates with a few clicks, and users download certificate packages ready to import into ATAK, iTAK, or WinTAK. Certificate renewal and revocation are handled through the same interface.
What protocol does Sit(x) use to communicate with TAK clients?
Sit(x) processes standard Cursor on Target (CoT) XML messages over TCP with mutual TLS (mTLS) authentication. This is the same protocol used by GOTS TAK Server, ensuring full compatibility with all TAK ecosystem clients and tools.
Does Sit(x) have an API?
Yes. Sit(x) provides a comprehensive REST API with OAuth 2.0 authentication. The API supports client credential grants for system-to-system integrations, device authorization flows for TAK client authentication, and SSO token exchange (SAML, OIDC, OAuth) for enterprise identity provider integration. API scopes control access to specific resources.
Can I integrate Sit(x) with external data sources?
Yes. Sit(x) supports data sync capabilities for Cursor on Target data integration. You can sync external CoT data and publish internal data to partner systems. Bridge adapters and the client API enable integration with non-TAK systems.
How does multi-tenant isolation work?
Each organization on Sit(x) operates within a completely isolated database schema. There is no co-mingling of data between organizations. Each organization has its own users, TAK groups, certificates, federation policies, and security settings. This isolation is enforced at the database level, not just the application level.
What authentication methods does Sit(x) support?
Sit(x) supports multiple authentication methods: username/password with enforced password complexity, SAML 2.0 SSO for enterprise identity provider integration (Entra ID, Okta, etc.), multi-factor authentication via authenticator app or SMS, and mutual TLS certificate authentication for TAK client connections.
Does Sit(x) support video streaming?
Yes. Sit(x) integrates video feed management, allowing you to connect live video streams from field cameras and drones into the common operating picture. Video feeds are managed through the admin dashboard and accessible to authorized users and TAK clients.
How are software updates handled?
Sit(x) uses continuous delivery to deploy updates and security patches automatically. Updates are applied without disruption to your operations. You always have the latest features and security fixes without any manual upgrade process.
Security & Compliance
Where is Sit(x) hosted?
Sit(x) is hosted exclusively on AWS GovCloud (US), an isolated cloud region operated by cleared U.S. persons on U.S. soil. AWS GovCloud is designed for ITAR-regulated workloads and maintains FedRAMP High authorization, supporting over 300 security controls.
Is Sit(x) FedRAMP authorized?
Sit(x) is hosted on AWS GovCloud infrastructure which holds FedRAMP High authorization. Sit(x) inherits these infrastructure-level security controls and implements additional application-level controls aligned with NIST 800-53 Rev 5. Contact our team for detailed security documentation and ATO support.
What compliance frameworks does Sit(x) support?
Through its AWS GovCloud hosting, Sit(x) supports FedRAMP High Baseline, DoD Impact Levels 4 and 5 (IL4/IL5), ITAR compliance, NIST 800-53 Rev 5, NIST 800-171 for CUI protection, FIPS 140-2 validated cryptography, CJIS Security Policy, and SOC 1/2/3 reporting.
How is data encrypted?
All data is encrypted at rest using AES-256 encryption and in transit using TLS 1.2 or higher. TAK client connections use mutual TLS (mTLS) with client certificates. Database backups are encrypted. Encryption keys are managed through AWS Key Management Service (KMS) within GovCloud.
Does Sit(x) support multi-factor authentication?
Yes. Sit(x) supports multi-factor authentication via authenticator app (TOTP) and SMS-based verification codes. Organizations can enforce MFA for all users through org-level security policies. Backup codes are available for account recovery.
What audit logging does Sit(x) provide?
Sit(x) logs all user logins (successful and failed), administrative actions, data access events, federation activities, device connections, and certificate operations. Audit logs are searchable through the admin dashboard and can be filtered by user, action type, and time range.
Can Sit(x) restrict logins by geographic location?
Yes. Sit(x) supports IP-based login origin restrictions that can block authentication attempts from unauthorized countries. Barred login attempts are logged for security review.
Still Have Questions?
Our team is happy to answer any questions about Sit(x), discuss your specific requirements, or schedule a personalized demo.