Six-year retention, WORM via S3 Object Lock, tamper-evident audit log, compliance-officer export to PDF/CSV.
SAML and OIDC SSO included. FIDO2 hardware keys. Smart cards. Biometrics on supported endpoints. JIT elevation for sensitive systems.
Session-anomaly engine flags off-hours sessions, atypical command sequences, unusual exfiltration patterns. SIEM-stream to Splunk, Session Monitor, QRadar.
Built for the regulated reality
Financial-services IT is the most-audited environment in business. Every desktop-support session into a trading desk, every help-desk touch on a wealth-management workstation, every back-office RDP jump leaves an artefact that a regulator can ask for years later. Silux Connect was built with that audit posture in mind. Session recordings are saved on your technicians' own computers, so they go into your own write-once archive — Silux never holds a copy. Audit-log entries are HMAC-chained so any tampering is detectable. Compliance-officer access is a separate role that can read audit evidence without elevating into the operational surface.
For broker-dealers and wealth managers under FINRA Rule 4511, the retention and review requirements are explicit and we map to them directly. Six-year WORM retention is the default. Quarterly review workflows can be assigned to compliance officers via the policy engine; review evidence is captured and timestamped. For SOX-bound public-company filers, our ITGC mapping covers access management, change management, computer operations and program development control objectives.
For PCI-DSS, our architecture is SAQ-D eligible. We don't store PAN data ourselves — payment cards go through Stripe and we never touch the cardholder data environment. For customers whose support sessions might land on a CDE workstation, our clipboard and file- transfer restrictions can be enforced per-tenant, with attempts to bypass them captured in the audit log and surfaced to compliance.
For trading-floor support, latency matters. Our us-east-1 relay sits in N. Virginia at sub-30ms round-trip from most Wall Street and Stamford addresses. AWS Direct Connect customers can ingress via PrivateLink for sub-15ms. The AI assistant runs locally on a per-tenant basis, so AI-assisted triage does not add network round-trips — critical during a market-hours desktop issue.
Meridian replaced a legacy bastion-host plus TeamViewer Corporate with Silux Connect across 340 trader workstations and an IT support team of 18. The principal driver was FINRA Rule 4511 retention evidence: the previous solution stored session logs in the technician's own Outlook archive, which their last examination cited as a deficiency. After migration, every session has a tamper-evident retention record, the compliance officer has a dashboard, and SOX walk-through testing now takes 18 hours instead of 64. Time-to-first-response on trading-floor incidents dropped from 7m12s to 2m44s.
Case-study draft. Customer review pending — illustrative figures only until the published reference is approved.
Frequently asked
Our architecture is PCI-DSS v4.0 SAQ-D eligible. Payment data tokenisation is via Stripe; we don't store PANs ourselves. Silux Connect is a support tool, not a payment processor, so the customer's CDE scope depends on what they do during sessions.
Audit logs can be retained for the FINRA-required six years. Session recordings are saved as files on your technicians' own computers, so they go straight into your existing write-once archive under your control — Silux never holds a copy. Audit-log entries are tamper-evident with HMAC chaining. Compliance-officer export to PDF and CSV is one click.
Our us-east-1 relay sits in N. Virginia with sub-30ms round-trip latency to most Wall Street and Stamford addresses. We support direct-private-link customer ingress for sub-15ms paths from your DC. The AI assistant's local LLM means AI features don't add network round-trips.
Yes. Our control mapping covers the FFIEC IT Examination Handbook (Operations, Information Security, Outsourcing) and the SOX ITGC categories (access management, change management, computer operations, program development). Available to qualifying customers under NDA.
Our session-anomaly engine flags unusual technician behaviour: off-hours sessions, atypical command sequences, unusual file exfiltration patterns, attempts to bypass clipboard restrictions. Alerts can fire to your SIEM or to a compliance-officer queue.