The assessor portal's browser-visible response headers name a common web stack. How should that fact be handled in PORP-scope website OSINT?
Select an answer to reveal the explanation.
Short Explanation
A stack header in the browser is like a brand sticker on a public kiosk — you can read it while walking past. Write the clue down. Turning that into a scan or an exploit against the assessor portal is pentest work, not PORP.
Full Explanation
Passive public clues such as headers already returned to a normal browser are in-scope website OSINT. Built-with-class awareness stays descriptive. Intrusive scans, exploit modules, or "fixing" production headers on the civic site are out of PORP. The researcher records the stack observation and leaves attack testing to authorized security teams.