Access and store isolation
Named people and service roles receive access for an approved purpose. Commerce Cockpit binds seller authorization and reads to the exact store, with denial checks for cross-store access.
Security
Protection shaped around each store.
Titan Link applies scoped access, credential protection and operational review to its marketplace software. These are the security practices for our current corporate and Commerce Cockpit validation scope.
Our approach
Report a security concern Keep access specific. Keep sensitive values contained.
Our security policies assign owners for access, encryption, endpoint standards, vulnerability review and incidents. Product controls are reviewed against the exact marketplace and store they serve.
Credentials and encryption
Admitted marketplace credentials stay server-side behind restricted access and an encrypted credential boundary. The checked validation host and recovery storage are encrypted, and public ingress uses HTTPS.
Network and endpoints
The Cockpit application listener is restricted behind reviewed HTTPS ingress and a controlled administration path. Company endpoints used for protected operations are governed by requirements for updates, malware protection, screen lock and disk encryption.
Monitoring and review
We route service alerts to a technical responder, review access and dependency advisories, record exceptions and assign remediation. Monitoring coverage is assessed against each operating system and service.
Incident response
Our incident procedure covers intake, severity, containment, evidence, owner and privacy decisions, provider or seller notification assessment, recovery and follow-up. External notice follows verified channels and an incident-specific decision.
Data and providers
We minimize marketplace data for approved read functions, separate product and store boundaries, and handle disconnection, retention and vendor copies through documented processes.
Scope of current validation
Commerce Cockpit's inspected controls apply to its current read-oriented validation runtime. Each new Production store, provider scope or credential lifecycle is reviewed before broader use. Security and privacy requests can also be routed through our support channels.