Cybersecurity
Preparing Security Evidence for Client Audits or Tenders
Clients and tender committees increasingly ask for security evidence, not just statements. This checklist maps ten kinds of evidence commonly requested and how to assemble them into one honest package.
SEO and Content Specialist
6 min read Reviewed by Legia Cybersecurity Team
Short answer: the security evidence an assessor accepts is dated documents and records showing that controls actually run, not a statement that the company is secure. Prepare ten kinds of evidence, assign an owner to each item, and write “not yet in place” when something is not. The exact requirements always follow the tender document or the client’s request.
Companies that serve large clients or join tenders often receive a security questionnaire with a short deadline. It holds dozens of questions, and the answers are scattered across several people’s heads. This checklist helps you assemble security documents for a tender or client audit before the request arrives, so that on deadline day you only pick files instead of hunting for them.
Security documents for a tender: what is usually asked
There is no single format. Requests usually come in three forms: a yes/no questionnaire, attached documents, and an interview or on-site check. Questionnaire authors often rely on public frameworks. CIS Controls v8.1 contains 18 controls, from asset inventory to penetration testing. The NIST Cybersecurity Framework 2.0 is designed to be usable by any organization, regardless of size, sector, or maturity. For cloud providers, the Cloud Security Alliance has the Cloud Controls Matrix with 197 control objectives in 17 domains, and its CAIQ questionnaire consists of yes/no questions.
You do not need to master all three. Use the CIS Controls as the skeleton of your checklist, then map every incoming question to one of the ten kinds of evidence below:
| Evidence | What can be submitted | Related CIS control |
|---|---|---|
| 1. Asset and software inventory | List of devices, servers, and licenses with last update dates | Inventory and Control of Enterprise Assets; Inventory and Control of Software Assets |
| 2. Accounts and access rights | List of roles and holders, records of deactivated leaver accounts, proof of two-step authentication on admin accounts | Account Management; Access Control Management |
| 3. Audit logs | Sample logs recording who changed what and when, with retention period | Audit Log Management |
| 4. Vulnerability management | Latest vulnerability assessment report, status of each finding, retest results | Continuous Vulnerability Management |
| 5. Backup and recovery | Backup schedule and the latest restore test record | Data Recovery |
| 6. Incident response plan | Plan document, contact list, exercise records | Incident Response Management |
| 7. Security awareness training | Dated materials and attendee list | Security Awareness and Skills Training |
| 8. Third parties | List of vendors that touch data, confidentiality agreements | Service Provider Management |
| 9. Security testing | Summary of the penetration testing report and note on closed findings | Penetration Testing |
| 10. Personal data | Data processing agreement and list of parties involved in processing | Not in CIS; see the PDP Law below |
Evidence is not a statement: three traits assessors check
Assessors distinguish “we have a policy” from “the policy is carried out”. Strong evidence has three traits:
- Dated. A document without a date cannot be judged as still valid or not.
- Shows execution. An account deactivation policy alone is not enough. A list of accounts deactivated last month with the dates the employees left shows the policy running. The workflow is covered in When to Deactivate a Departing Employee’s Accounts.
- Has an owner. Each piece of evidence has one person who can explain it when asked. For logs that record data changes, see Role-Based Login and Activity Logs.
Security testing reports: the part most often requested
Evidence 4 and 9 usually take the longest to prepare, because they depend on the testing party and on fix time. A report describes the system at the time of testing, so schedule testing well before the deadline so that fixes and a retest can finish. How to hand over a report without exposing a map of your system’s weaknesses is covered in Can a Penetration Testing Report Be Used for a Tender, and the difference between the two kinds of testing in Vulnerability Assessment or Penetration Testing.
Personal data: if you process data on behalf of clients
If you process personal data on behalf of a client, Law No. 27 of 2022 on Personal Data Protection regulates the processor role in Article 51. A processor must process data on the instruction of the data controller, and responsibility for that processing rests with the controller. A processor that engages another processor needs the controller’s written approval, and a processor that processes beyond the instructions and purposes set by the controller becomes responsible for that processing. So prepare a data processing agreement and a list of the parties involved in processing. This summary is for technical planning, not legal advice.
How to assemble the evidence package
- Collect the requests. Copy all the questions from clients and tenders you have received, then map them to the ten kinds of evidence above.
- Assign an owner for each kind of evidence, one person per item.
- Add dates and a review schedule. Record when each file was created and when it needs updating.
- Mark what is missing. Write “not yet in place” with a plan and target date. An honest answer is safer than a claim that collapses under inspection.
- Do not state what you do not hold. Do not write certifications or compliance with standards you do not hold. Write “mapped to” only when the mapping was actually done.
- Hand over through a restricted channel. Security evidence contains system details, so hand it over under a confidentiality agreement, not as a general attachment.
How Legia helps
For evidence 4, a Legia Vulnerability Assessment report contains a summary for management, a list of findings ranked by CVSS severity with evidence and location, remediation steps, a list of assessed assets with dates and scope, and retest results that are included in the package. The whole process generally takes 2 to 4 weeks, and testing only starts after written permission from the system owner. Each auditor’s requirements differ, so share the requirements you received in the consultation session so that the fit is confirmed before the assessment starts. Other services in this pillar are on the Cyber Security page. A template incident plan for evidence 6 is in Cyber Incident Response Plan.
Frequently asked questions
Can a company without ISO 27001 certification join a tender?
The tender document decides. If certification is required, no document substitutes for it. If what is asked is evidence of security controls, the package above is what you use, and a company must not state a certification it does not hold.
How recent must the evidence be?
There is no official validity period, and the accepted period follows each request. Most audit requirements ask for a vulnerability assessment once a year, and every major change to the system makes an old report less representative.
What if a control is not in place yet?
Answer “not yet in place”, attach a plan and completion date, then do the work. A claim that falls apart on inspection undermines trust in all your other answers, while a control admitted to be incomplete can still be assessed together with its plan.
Who should own the evidence package?
One person, usually the IT manager or security lead, as the compiler. The owner of each item remains the person who runs the control, so that interview answers come from whoever understands it best.
Sources
- CIS Controls v8.1, list of 18 controlscisecurity.org
- NIST, The NIST Cybersecurity Framework (CSF) 2.0csrc.nist.gov
- Cloud Security Alliance, Cloud Controls Matrix and CAIQcloudsecurityalliance.org
- Law No. 27 of 2022 on Personal Data Protection, JDIH BPKperaturan.bpk.go.id
- Text of Article 51, Law 27/2022pasal.id

