Free printable checklist

Infrastructure Evaluation Checklist

A 10-minute self-assessment for founders: is your infrastructure cost-effective, secure and scalable?

40 plain questions across cost, security, scale and governance, scored Yes, Partly or No. No deep technical digging: if you do not know an answer, ask your team.

Updated for 2026: phishing-resistant sign-in, AI and LLM keys, software bills of materials and the current ISO/IEC 27001:2022 edition.

Last reviewed: November 2026. 4 pages, A4. 40 questions, 80 points.

Download PDF

Score it here

The same 40 questions as the PDF. Your answers stay in this browser while you fill it in.

How to score

Yes = 2Partly = 1No = 0

Tick one box per line. Add up each section (5 lines, so 10 points at most), then add the 8 sections.

Does a line not apply to you (for example, you do not run virtual machines)? Score it 2, so it does not pull you down.

Section 1 · Cost

Cost visibility

Do we know where the money goes?

0 / 10

0 of 5 answered

  1. 1.1We can see monthly cloud cost by service and by team or product.
  2. 1.2Budgets and alerts warn us before a surprise bill, not after it.
  3. 1.3Idle and unused resources are found and removed on a schedule.
  4. 1.4Someone acts on the provider's right-sizing recommendations at least once a quarter.
  5. 1.5We know roughly what one customer, feature or environment costs us.

Section 2 · Cost

Cost leaks

Where does money leak without anyone noticing?

0 / 10

0 of 5 answered

  1. 2.1Non-production environments shut down outside working hours.
  2. 2.2Steady, always-on workloads are covered by Savings Plans, reservations or committed-use discounts.
  3. 2.3Servers run on current instance generations, and Arm (AWS Graviton) has been tried where our software supports it.

    Example: AWS M8g runs on Graviton4.10

  4. 2.4We count our public IPv4 addresses and release the ones we do not need.

    Since 1 Feb 2024 AWS charges for every public IPv4 address, in use or idle.8

  5. 2.5Every resource carries an owner and cost-centre tag, and untagged resources are blocked or flagged.

Section 3 · Security

Identity, access and secrets

Could a stolen password or leaked key take us down?

0 / 10

0 of 5 answered

  1. 3.1Everyone with admin or cloud-console access signs in with phishing-resistant MFA: passkeys or FIDO2 security keys, not SMS codes.

    NIST SP 800-63B-4 requires a phishing-resistant option at AAL2 and a phishing-resistant authenticator at AAL3.1

  2. 3.2Least privilege: no broad admin roles for people or services, and access is reviewed at least quarterly.
  3. 3.3The root or owner account is locked away with MFA and not used day to day.
  4. 3.4Secrets live in a secrets manager, not in code, CI variables, wikis or chat.
  5. 3.5AI and LLM API keys are in the secrets manager too, with spend limits and a rotation plan.

    OWASP Top 10 for LLM Applications 2025: LLM10 Unbounded Consumption.3

Section 4 · Security

Data and workload protection

If someone gets in, how far can they get?

0 / 10

0 of 5 answered

  1. 4.1Data is encrypted at rest and in transit, everywhere.
  2. 4.2On AWS, every EC2 instance requires IMDSv2 (the metadata token), and the account default enforces it.

    AWS documents how to require IMDSv2 and enforce it at account level.2

  3. 4.3Production is on a separate network (and ideally a separate account) from dev and staging.
  4. 4.4We have written rules for what data may go into AI prompts: no secrets and no customer personal data unless approved.

    OWASP Top 10 for LLM Applications 2025: LLM02 Sensitive Information Disclosure.3

  5. 4.5Audit logs are on, protected from deletion, and kept long enough for our obligations.

    In India, CERT-In Directions require ICT logs for a rolling 180 days, kept within India.9

Section 5 · Security

Software supply chain

Do we know what is inside what we ship?

0 / 10

0 of 5 answered

  1. 5.1Code and dependencies are scanned automatically in CI/CD.
  2. 5.2Container images are scanned before they reach production.
  3. 5.3Each release produces an SBOM (software bill of materials) that we could hand to a customer.

    CISA, 2026 Minimum Elements for an SBOM (29 July 2026).4

  4. 5.4We can prove where, when and how each build artifact was produced (build provenance).

    SLSA v1.0 provenance.5

  5. 5.5Patch deadlines for critical and high vulnerabilities are written down and met.

Section 6 · Scale

Scalability

What breaks first if traffic doubles next month?

0 / 10

0 of 5 answered

  1. 6.1Compute and the application tier scale automatically with load.
  2. 6.2We have a load-test baseline and a capacity plan for expected growth.
  3. 6.3The database has a plan for read scaling, connection limits and backups.
  4. 6.4Caching or a CDN sits in front of static content and heavy reads.
  5. 6.5Performance is measured against service level objectives (SLOs) for the user journeys that matter.

Section 7 · Scale

Reliability and recovery

When something fails at 2 am, what happens?

0 / 10

0 of 5 answered

  1. 7.1Monitoring and alerts go to a named on-call owner.
  2. 7.2Backups are proven by real restore drills, not just by the backup job's success message.
  3. 7.3Every deployment can be rolled back quickly.
  4. 7.4Recovery time and data-loss targets (RTO and RPO) are written down for critical systems.
  5. 7.5There is a written incident response process, and every incident ends with a review and tracked actions.

Section 8 · Governance

Governance and assurance

Could we pass a customer's security review?

0 / 10

0 of 5 answered

  1. 8.1Infrastructure is defined as code (for example Terraform, OpenTofu or CloudFormation), and that code is the source of truth.
  2. 8.2High-risk changes need a second person's approval.
  3. 8.3Dev, staging and production are built the same way.
  4. 8.4Every access and change to production can be traced to a person and a time.
  5. 8.5We know which assurance our customers ask for (ISO/IEC 27001:2022, SOC 2) and check ourselves against it each quarter.

    ISO/IEC 27001:2013 certificates expired or were withdrawn after 31 October 2025 (IAF MD 26).6 SOC 2 reports come from a CPA examination (AICPA).7

Your result

0 of 40 answered

Answer all 40 and your total and band show here straight away.

Sources (checked November 2026)

  1. NIST SP 800-63B-4, Digital Identity Guidelines: Authentication (final, July 2025). csrc.nist.gov/pubs/sp/800/63/b/4/final
  2. AWS, Modify instance metadata options (require IMDSv2). docs.aws.amazon.com/AWSEC2/latest/UserGuide/configuring-IMDS-existing-instances.html
  3. OWASP Top 10 for LLM Applications 2025. genai.owasp.org/llm-top-10/
  4. CISA, 2026 Minimum Elements for a Software Bill of Materials. cisa.gov/sites/default/files/2026-07/2026_cisa_sbom_minimum_elements_508c.pdf
  5. SLSA v1.0, Provenance. slsa.dev/spec/v1.0/provenance
  6. IAF MD 26:2023, Transition requirements for ISO/IEC 27001:2022. iaf.nu/iaf_system/uploads/documents/IAF_MD26_Issue_2_15012023.pdf
  7. AICPA, SOC 2 examinations. aicpa-cima.com/topic/audit-assurance/audit-and-assurance-greater-than-soc-2
  8. AWS, Public IPv4 address charge (from 1 February 2024). aws.amazon.com/blogs/aws/new-aws-public-ipv4-address-charge-public-ip-insights/
  9. CERT-In Directions under section 70B(6) of the IT Act, 28 April 2022. cert-in.org.in/PDF/CERT-In_Directions_70B_28.04.2022.pdf
  10. AWS, Amazon EC2 M8g instances. aws.amazon.com/ec2/instance-types/m8g/

Want us to go through it with you? Free 20-minute review