You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit e7127a1
Browse filesBrowse the repository at this point in the historyBrowse files
Let each test account say what it may and may not do, and judge cross account findings by it
The cross account access checks could prove one account reached another's object,
but not whether that was wrong: a read only auditor is meant to see everything,
and reporting it as a bug is noise. Now each test account, the first and the
second, has a field for what that login should and should not be able to do.
The compare check carries both descriptions into the finding, states them in the
evidence, and frames the question: is the first account reaching this object
within what it is meant to do, or not. The enhanced review is given the same
two descriptions and told to decide, calling it a false positive when the access
is within the stated role and a real broken access control when it is outside
it, or asking a person to confirm when no role was given. The two proof
screenshots, what each account sees, stay for a person to compare alongside it.
Copy file name to clipboardExpand all lines: app/web/templates/external_site.html
+8Lines changed: 8 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -428,6 +428,10 @@
428
428
<label>User name field <input type="text" name="auth_username_field" maxlength="100" value="{{ auth.username_field if auth and auth.username_field else '' }}" placeholder="found on the page"></label>
429
429
<label>Password field <input type="text" name="auth_password_field" maxlength="100" value="{{ auth.password_field if auth and auth.password_field else '' }}" placeholder="found on the page"></label>
placeholder="e.g. a standard user: should see only its own orders and profile; should not see other customers or any admin page.">{{ auth.intent if auth and auth.intent else '' }}</textarea>
434
+
<span class="faint small">Optional. Used by the compare checks and the AI review to tell a real access violation from expected, shared access.</span></label>
431
435
<div class="faint small">Use a test account. A signed in scan can change what that user can change.</div>
432
436
</details>
433
437
<details class="hand-fields" {{ 'open' if auth_b }}>
@@ -455,6 +459,10 @@
455
459
<label>User name field <input type="text" name="auth_b_username_field" maxlength="100" value="{{ auth_b.username_field if auth_b and auth_b.username_field else '' }}" placeholder="found on the page"></label>
456
460
<label>Password field <input type="text" name="auth_b_password_field" maxlength="100" value="{{ auth_b.password_field if auth_b and auth_b.password_field else '' }}" placeholder="found on the page"></label>
457
461
</div>
462
+
<label>What the second account should and should not do
placeholder="e.g. a read-only auditor: may view all records but must not edit; or a different standard user that owns different data than the first.">{{ auth_b.intent if auth_b and auth_b.intent else '' }}</textarea>
465
+
<span class="faint small">The compare checks and the AI review weigh a cross-account read against this, so an auditor that is meant to see everything is not reported as a bug.</span></label>
458
466
<div class="faint small">Use a second test account that owns different data than the first. That is what lets the compare checks prove one account can reach the other's objects.</div>
0 commit comments