Home › Security

Security

QULDEX security: how your audit evidence is protected

In shortQULDEX security rests on three things. Every evidence file is encrypted before it is stored. Each organisation's data is kept separate from every other organisation's. Every view and download of a file is recorded. Customer data is stored on Amazon Web Services in India, and payments are handled by Razorpay.

Which security controls protect audit data in QULDEX?

Six controls the platform applies today, described at a high level. Each lists the ISO/IEC 27001:2022 and SOC 2 criteria it relates to, so your reviewers can map it to their own questionnaire.

Encryptedevery evidence file, at rest and in transit
Separatedeach organisation sees only its own data
Recordedevery view and download of a file
Indiacustomer data hosted on AWS

Evidence encryption

Every evidence file is encrypted before it is stored.

  • Encrypted at rest with AES-256
  • Encrypted in transit over HTTPS
  • Each file is checked for tampering when it is opened
Relates toISO A.8.24SOC 2 CC6.1

Viewing and download control

Read evidence without copies leaving the platform.

  • Files open in a secure in-browser viewer
  • Each audit decides who may download
  • Every view and download is recorded
Relates toISO A.5.12ISO A.8.3SOC 2 CC6.1

Separation and roles

Your organisation's data is visible only to your organisation.

  • Each organisation's data is kept separate
  • Role-based access for every user
  • Restricted audits are visible only to their audit team
Relates toISO A.5.15ISO A.8.3SOC 2 CC6.1

Sign-in and sessions

Access that ends when you sign out.

  • Signing out ends the session everywhere
  • Repeated sign-in attempts are limited
  • Passwords are never stored in readable form
Relates toISO A.8.5ISO A.5.17SOC 2 CC6.1

Activity logging

A record of who did what, for your auditors.

  • Sign-ins, data access and permission changes are logged
  • Your administrator sets how long logs are kept
  • Evidence access is shown per person
Relates toISO A.8.15ISO A.8.16SOC 2 CC7.2

Application and network

Protected by default.

  • HTTPS only
  • Uploads are checked before they are stored
  • Payments are handled by a specialist provider
Relates toISO A.8.20ISO A.8.26SOC 2 CC6.6

"Relates to" shows where a control fits those criteria. It is not a statement of certification or compliance.

How is one evidence file protected, from upload to report?

The same six steps run for every file, on every plan.

  1. UploadThe file is checked before it is accepted.
  2. EncryptIt is encrypted before it is stored.
  3. StoreThe encrypted file is stored on AWS in India.
  4. CheckOpening it checks your organisation, role and audit team.
  5. ViewIt opens in a secure viewer. Download only if the audit allows it.
  6. RecordEvery view and download is recorded.

See the Secure Evidence Vault →

Where is QULDEX data stored?

DataWhereProtection
Audits, controls, findings, usersAmazon Web Services (Amazon RDS), IndiaEncrypted in transit; access limited to the QULDEX service
Evidence filesAmazon Web Services (Amazon S3), IndiaEncrypted before storage
WebsitesCloudflareHTTPS only
Card paymentsRazorpayCard data never reaches QULDEX servers

Activity logs are kept for the period your administrator sets (default 90 days). Evidence retention, backup and exit terms are set out in your agreement; ask us for the current terms.

Which companies process data for QULDEX?

The main providers that store or process customer data.

ProviderPurposeCustomer dataLocation
Amazon Web ServicesDatabase (Amazon RDS) and evidence file storage (Amazon S3)All customer dataIndia
CloudflareWebsite delivery and protectionPasses through in transitGlobal network
RazorpaySubscription paymentsBilling contact and payment detailsIndia

A full list of providers is available to customers on request.

What does QULDEX do, and what do your administrators control?

QULDEX does

  • Encrypts every evidence file and checks its integrity on every open
  • Keeps each organisation's data separate, enforced on the server for every request
  • Records every evidence view and download
  • Ends sessions on sign-out and limits repeated sign-in attempts
  • Runs the service over HTTPS only

Your administrators decide

  • Who belongs to each audit team, and each person's role
  • Whether an audit's evidence can be downloaded, by team, lead only or everyone
  • How each file is classified: public, internal, confidential or restricted
  • How long activity logs are kept
  • Removing people promptly when they leave

Which security documents can I request?

Shared with prospects and customers under a non-disclosure agreement.

Under NDAInformation security policiesAccess control, encryption, incident response, retention.
Under NDAArchitecture overviewHow data flows through the platform and how it is protected.
Ask usOther documentsFor a completed security questionnaire or test summaries, ask and we will tell you what is available.
Request by email:security@egvservices.comOpen email

How do I report a security issue to QULDEX?

01

Write to us

Include steps to reproduce. Please don't access other customers' data while testing.

security@egvservices.com
02

Disclosure policy

Scope, safe harbour and what to expect after you report.

Read the policy →

03

Service status

Status for the app, the API and the Evidence Vault.

Open the status page →

QULDEX security: common questions

Where is QULDEX data stored?

Customer data is stored on Amazon Web Services (AWS) in India.

How is evidence encrypted?

Every evidence file is encrypted with AES-256 before it is stored, and all traffic uses HTTPS.

Can another organisation see our evidence?

No. Each organisation's data is kept separate. Within your organisation, audit teams, roles and the download setting decide who sees what.

QULDEX supports 51 frameworks. Is QULDEX certified to all of them?

No. Supporting a framework means the platform helps your team audit against it. Ask us for QULDEX's own current certifications.

How do I report a security issue?

Email security@egvservices.com with steps to reproduce, and read the responsible disclosure policy for scope and safe harbour. Please don't access data that isn't yours while testing.

Related

Bring your security questionnaire

Walk through the controls with us against your own review checklist.

Schedule
Book a Demo