テーマ： authorization
-
Choosing permission checkpoints for queued jobs after access is revoked
Make the timing of authorization explicit when a request schedules work that runs later. The proposed exercise separates permission to enqueue work from permission to execute it and retrieve its output.
-
Testing that an emergency bypass ends when its authorization ends
Check the lifecycle of an explicitly approved emergency bypass in a controlled environment. The proposed method distinguishes ordinary authorization, temporary exceptional authority, and the return to ordinary policy.
-
Keeping authorization enforced when dependencies fail
Test the security decision made when a required dependency is unavailable. This original fault-injection proposal makes fail-open behavior visible without assuming that every service should return the same error or availability response.
-
Testing that profile updates cannot assign privileged account fields
Create a narrow regression for updates that accept ordinary profile data alongside fields the caller must not control. The method proposes explicit field ownership rather than a generic input-validation checklist.
-
Token passthrough and the confused deputy in MCP servers that call other APIs
An MCP server that forwards a client's token to a downstream API, or that uses its own broad credentials on behalf of whoever asks, lets callers act with authority they were never granted. The MCP security guidance forbids token passthrough and describes the confused-deputy flow for proxy servers.
-
Testing continuation cursors after the requesting identity changes
Check the application’s visibility policy when a continuation cursor is reused under a different principal. This original method treats the cursor as part of a query context whose security meaning must be specified.
-
Testing authorization for workflow transitions instead of screen access
Check whether a caller may perform a particular state transition, including transitions not exposed by the current interface. This proposed methodology targets approval workflows whose security policy depends on both identity and current state.
-
Checking who may restore a deleted object and its former permissions
Treat restoring a deleted object as a new authorization decision with explicit permission semantics. This proposed fixture targets the gap between deletion policy and restoration behavior.
-
Testing configuration changes that alter another user’s authority
Identify configuration writes that indirectly grant permissions even when their endpoint looks like ordinary settings editing. This proposal follows the resulting authority change rather than judging risk from the route name.
-
Testing private export access from request to eventual deletion
Follow a private export through generation, retrieval, expiry, and cleanup. The proposed method checks the entire artifact lifecycle rather than treating a successful authorization check at export creation as sufficient.
-
Distinguishing denied access from a broken negative-test fixture
Prevent an agent from treating any error as proof that an access-control test passed. The proposed method uses matched controls to identify whether the application actually reached the intended authorization decision.
-
Testing authorization through resource relationships rather than role names
Check whether a caller can act on a particular object through the relationship the product actually promises. This proposed lab method treats role labels as fixture attributes, not as the test oracle.
-
Separating the acting service from the represented user in delegation tests
Test a delegated action with both the executing service identity and the user it represents visible in the oracle. This proposed method avoids treating successful service authentication as sufficient proof of user authority.
-
Checking that nested resource routes bind children to the stated parent
Validate a relationship that coding agents can omit when building nested endpoints: the requested child must belong to the requested parent under the application contract. This is an original fixture design.
-
Defining the authorization oracle for mixed-object batch requests
Expose ambiguous access rules in batch operations before an agent writes tests that approve whichever response the implementation happens to return. The proposal focuses on mixed ownership within one request.
-
Verifying invitation acceptance against the intended recipient and workspace
Test the binding between an invitation, its intended recipient, and its destination workspace. The proposed regression is aimed at agent-written onboarding flows that otherwise test only successful acceptance.
機械可読： JSON