A Green Security Questionnaire Can Hide an Untested Permission Change

Author: OmniStack

Published at: 11/07/2026

A Green Security Questionnaire Can Hide an Untested Permission Change

The buyer problem: a questionnaire can be true and still incomplete

A green security questionnaire does not show that the next release tested its changed permission paths. Consider a hypothetical multi-site operations platform whose annual questionnaire says users can access only authorised records. The statement can be accurate at the process level. In the next release, a supervisor workflow adds a report export for location managers, and the export returns records from a second business unit because that path was not included in the release test set.

The defect does not need to look dramatic. The HTTP response can be successful. The role can be present in the identity provider. The policy can say that access is restricted. None of those facts answers the release question: did this specific subject, object and operation receive the right test and review before users received it?

For an Australian or Singapore CTO, CIO or multi-site operations leader, the practical artefact is security questionnaire release evidence. It connects the assertion already given to a changed route, resolver, report, export, background job, cache key or administrative action. Without that connection, the questionnaire describes intended process and control intent while the release may contain an untested path.

That distinction matters when a platform serves staff across branches, warehouses, tenants or legal entities. A permission change can alter who sees a customer account, who approves a refund, which location receives a shipment record, or whether a support user can impersonate another tenant. The business impact sits in the changed workflow, not in the wording of the questionnaire.

A checked control box is therefore a starting point for review. It is not release approval.

Separate standing assertions from release evidence

A standing assertion describes how the organisation intends to operate. Release evidence shows how a particular change was examined. Treating the two as interchangeable is the root of many weak security reviews.

  • Standing assertion: the application uses role based access control.
  • Release evidence: the changed supervisor report was tested for the intended roles, tenant boundaries, fields and export operation.
  • Standing assertion: privileged access is controlled.
  • Release evidence: the new support override has a reviewer, a test result, an owner and a defined review or expiry condition.
  • Standing assertion: security issues receive risk review.
  • Release evidence: a failed or skipped authorisation case has a documented mitigation, residual risk response and retest trigger.

NIST SSDF 1.1 gives useful structure here. Its practices frame secure software development as producing, protecting, responding to and improving software. For this topic, the useful mechanisms are recording risk responses and re-evaluating exceptions. SSDF does not prescribe one expiry timer, one scoring formula or one approval workflow. It supports the need for a release record that keeps residual risk beside the decision.

OWASP ASVS serves a different purpose. It provides application security verification requirements. For this article, the relevant family is authorisation, especially access decisions across users, roles, functions and objects. Pin the ASVS version before converting it into a test request. Alignment can structure the evidence pack; it does not show that every access path has been checked or that cross-tenant access cannot occur.

For teams maintaining a legacy application or adding cloud services around it, this separation prevents a familiar failure mode. A policy remains green because it was reviewed at the organisation level, while a new GraphQL resolver, scheduled task or data export bypasses the enforcement point demonstrated in earlier evidence. The release diff is where the buyer should look.

Authorisation testing belongs in the delivery workflow, not only in an annual questionnaire response. A proposed quality assurance and testing capability can help a delivery team maintain the test evidence, but the buyer still needs to define which business rule must be checked and who can accept residual risk.

Find the permission change before choosing the test

The method fails when teams start with a generic control list. The right order is to identify the changed capability, map its subjects and objects, locate trust boundaries, find the enforcement point, and only then choose positive and negative cases.

A common counter-argument is that a full release diff is too broad for a busy product team. That is true if the diff is treated as a complete application security assessment. It is not true when the review is scoped to changed authorisation surfaces. A new role, route, resolver, report, field, queue consumer, cache key, support override or bulk action is a concrete trigger. The team does not need to retest every function because one permission changed. It does need to identify every path through which that permission can reach data or an operation.

Use this decision flow for a hypothetical release:

  1. Identify the capability. Write what the release now allows, such as a supervisor exporting shipment records or a finance user approving a refund.
  2. Identify the subject. Name the human role, service account, integration account, background worker or support identity making the request.
  3. Identify the object. Name the order, refund, shipment, tenant, location, account, report row or customer record affected.
  4. Identify the operation. Record whether the change permits read, create, update, approve, export, cancel or impersonate.
  5. Locate enforcement. Find where the decision occurs in the controller, service, resolver, policy layer, queue worker, scheduled task, cache lookup or database query.
  6. Choose test cases. Include an authorised path and a deliberately unauthorised path, with tenant, business unit, field and asynchronous boundaries where relevant.
  7. Record the decision. Attach the reviewer, skipped cases, findings, exceptions, mitigation, retest condition and acceptance owner to the release.

The enforcement step deserves special attention. A controller-level demonstration does not establish that a queue worker applies the same business rule. A cache key that omits the subject or tenant can return a valid result to the wrong requester. A bulk action can use a wider query than the screen that initiated it. A support override can be technically controlled while remaining permanently enabled.

For APAC buyers with regulated, contract-sensitive or operationally critical systems, accountability cannot be outsourced through a questionnaire. The exact policy interpretation depends on the buyer and the service arrangement. The operational decision is narrower and concrete: the accountable business must know what changed, what was tested and who accepted any residual risk.

Engineers trace a new permission path through an access-control maze before selecting tests.

Build the proposed questionnaire versus release gap map template

The most useful working document is a proposed gap map template that places the questionnaire assertion beside the release diff and the evidence needed to support approval. It is not an audit opinion or a universal control model. It is a way to expose where a true policy statement has no release-specific proof.

Questionnaire assertion

Release diff to inspect

Evidence to request

Gap if missing

Buyer decision

Users only access authorised records

New role, route, resolver, report, queue worker or bulk action

ASVS-aligned positive and negative tests for subject, object, operation and field access

The policy may be true while the changed path is untested

Accept, request retest or defer release approval

Privileged access is controlled

New admin permission, escalation rule or support override

Reviewer note, test result and expiry or exception record where applicable

Temporary privilege can become a silent standing permission

Require owner and review condition before acceptance

Security issues are risk reviewed

Known failed or skipped authorisation case

Risk response, mitigation and retest trigger consistent with SSDF mechanisms

A finding can be accepted without a closure path

Accept with condition, pilot or reject

Label this as a proposed template in the operating procedure, not as a vendor deployment record. The point is not to make every organisation use the same fields. The point is to stop the questionnaire from becoming the last place anyone looks after a permission-affecting change.

For each row, attach the release identifier and the actual code or configuration surface inspected. "Access control tested" is too vague. "Supervisor export for shipment records tested against location scope in the report service and asynchronous export worker" gives a reviewer something to challenge.

The gap map should also distinguish a finding from an exception. A failed authorisation test is a finding. Proceeding despite that finding is a risk response or exception. The exception needs an owner, business impact, mitigation and a renewal or expiry condition. The release may proceed under a controlled decision, or it may be deferred. What makes the evidence weak is not that every finding must block every release. It is the absence of an accountable closure path.

Related:dedicated engineering team capacity, relevant when the release team needs sustained QA, engineering and evidence ownership without splitting the roadmap across short-term contractors.

Negative tests matter more than happy-path demonstrations

A positive test demonstrates that the intended user can perform the intended operation. A negative test examines whether the same path rejects the wrong subject, object, tenant, field or execution context. For a permission change, the negative cases usually tell the buyer more.

In a hypothetical logistics platform adding a supervisor action to view shipment exceptions, the positive test might show that a supervisor at Location A can view an exception assigned to Location A. That is necessary. It does not examine the failure modes created by the new capability.

  • An unauthorised role attempts the new action and receives the expected rejection.
  • An authorised supervisor requests an exception belonging to a different tenant or business unit.
  • A permitted user requests a hidden field through an export, API response or report filter.
  • A background job processes an object outside the worker's assigned scope.
  • A cached result created for one subject is reused for another subject or location.
  • A bulk action includes records that the visible screen would have excluded.
  • A support user invokes an override without the required reason, approval or audit record.

These tests should name the subject, object and operation. "Role denied" is not enough if the real risk is that the correct role can read the wrong tenant. "Export blocked" is not enough if the export worker receives a broader query than the interactive report.

Asynchronous work deserves its own evidence. A queue consumer may not receive the same authorisation context as the request that created the message. A scheduled task may use a service account with broad access. A cache may preserve a response after the user's role or location scope has changed. The reviewer should ask where the business rule is enforced and what identity or scope travels with the work.

Finite tests do not prove absence of access defects. They show that named paths were checked against a stated rule at the time of review. That narrower claim is credible and useful. It also tells the buyer what monitoring, incident response and future regression testing must cover.

For a team that owns both application changes and cloud and DevOps delivery controls, the evidence can be attached to the pull request, deployment record and post-release review. The ownership model matters more than the tool. A green dashboard without the changed path is still a green dashboard without release evidence.

Authorized and unauthorized users face different outcomes at shipment access gates.

What to ask the team before signing the release

Before approving a permission-affecting release, ask for the changed access surface, the pinned verification reference, the test results, the unresolved gaps and the named acceptance owner. This turns a security questionnaire release evidence review into a decision a CTO, CIO or operations leader can inspect.

Ask the delivery team to provide the following as a proposed evidence pack template:

  1. Changed permissions. Identify new or modified roles, policies, routes, resolvers, reports, fields, exports, queue consumers, scheduled tasks, cache keys and administrative paths.
  2. Subject and object map. State which identities can act on which records, tenants, locations, business units and fields.
  3. ASVS reference. Pin the ASVS version and identify the authorisation requirements used to structure the tests, including the relevant OWASP ASVS 5.0 V8 Authorization section where applicable. Do not accept a generic claim that the release satisfies ASVS.
  4. Test location and result. Provide the test environment, build or release identifier, reviewer and evidence for both positive and negative cases.
  5. Skipped cases. Record what was not tested and why. A skipped asynchronous path is a release fact, not a detail to hide in a meeting note.
  6. Exception record. For each failed or skipped case that does not block release, name the owner, mitigation, business impact, renewal or expiry condition and retest trigger.
  7. Acceptance owner. Identify the person authorised to accept residual risk. Engineering can explain the implementation; operations, product, security or the accountable executive may need to decide whether the business can accept the exposure.

A dedicated engineering team from OmniStack can be an option for producing and maintaining this evidence when the buyer wants a stable team aligned to the product roadmap. That does not move risk acceptance outside the buyer's organisation. In-house ownership wins when policy interpretation, operating risk and acceptance authority sit inside the business, or when the system is sensitive enough that the accountable team must control every decision directly.

For a multi-site operator, make the acceptance owner explicit at the business boundary. Engineering may show that a supervisor role behaves as designed. Operations may decide whether visibility across all locations is appropriate. Security may require another negative test. Product may approve a phased pilot. Those are different decisions and should not be collapsed into a single green questionnaire answer.

Where the map stops

The proposed gap map template is a release review tool, not an audit opinion, legal opinion or proof that every access path is safe. It does not replace production monitoring, incident response, vulnerability management, contract obligations or the buyer's own interpretation of applicable requirements.

It also stops at the evidence available. If the team cannot identify the changed permission surface, the reviewer cannot infer coverage from a policy statement. If the system has undocumented legacy paths, the correct decision may be to defer the release, restrict the rollout, add monitoring or commission deeper testing. A green questionnaire cannot compensate for an unknown enforcement point.

Do not present the proposed template as an OmniStack deployment. Do not treat selected ASVS checks as company-wide security evidence. Do not treat SSDF alignment as an approval outcome. The useful claim is narrower: the map makes the relationship between a questionnaire assertion and a specific release decision visible.

For the next release that changes access, the accountable owner should decide whether to require a completed subject, object and operation map with positive and negative evidence. If the existing questionnaire remains the only evidence, record that the specific permission change has not been checked through this release method and make the release decision on that basis.

Sources and limits