This website
tekansa.com is a static marketing site. It holds no customer data, has no login, and runs no database of its own. Pages are served over HTTPS with modern TLS, and the enquiry form and concierge chat are the only places anything is entered.
Because there is no account system here, there is no password to breach and no session to hijack. What you type into a form is covered by the Privacy Policy.
How we work on client systems
The practices below are how we build, not a marketing list. They apply to the platforms we deliver and to our own internal estate.
Least privilege by default
Access is granted per role and reviewed, not handed out permanently. Production access is separated from development access.
Encryption in transit and at rest
TLS everywhere, and encryption at rest in the systems that hold data. Keys are managed by the platform, not by people.
Secrets are never in source
Credentials live in a secret manager, are rotated, and are kept out of repositories, logs and error reports.
Change control that works
Peer review on every change, automated tests in CI, progressive rollout behind feature flags, and rollback designed in from the start rather than improvised during an incident.
Dependencies are watched
Automated dependency and vulnerability scanning, with patching treated as routine maintenance rather than an emergency.
Logging and monitoring
Audit trails for privileged actions, and alerting designed to tell us something true in the first hour of an incident.
Regulated environments
Where an engagement is bound by HIPAA, GDPR, DORA, PCI DSS or similar, the controls and the evidence for them are engineered into delivery rather than assembled afterwards for an audit.
Certifications
We operate to HIPAA-aligned and GDPR-aware practices, and run internal programmes modelled on SOC 2 and ISO 27001. Where a specific certification is a requirement of your engagement, ask us directly and we will tell you plainly what we hold today and what we do not, rather than implying more than is true.
Reporting a vulnerability
If you believe you have found a security issue in this website or in anything we run, we want to hear about it. Write to hello@tekansa.com with enough detail to reproduce it.
Please give us a reasonable opportunity to fix the issue before disclosing it publicly, and avoid privacy violations, data destruction or service degradation while investigating. We will not pursue legal action against anyone who reports in good faith and follows that.
We aim to acknowledge a report within two working days and to tell you what we intend to do about it within ten. We do not currently run a paid bug bounty, and we will credit you if you would like us to.
Contact
Security questions, due-diligence questionnaires and vulnerability reports all go to hello@tekansa.com.