Occupancy-licensing staff install random OSINT toolbars from a blog into the city's main Chrome browser. What lab-software hygiene should they follow instead?
Select an answer to reveal the explanation.
Short Explanation
Mystery toolbars in the city's real Chrome are strangers with keys to the production cookie jar. A blog is not a software-vetting process. OSINT add-ons live in a controlled lab browser, not on the licensing desktop everyone uses for official work.
Full Explanation
Unknown browser extensions on a production civic browser are both an OPSEC and a security failure. Toolbars can read sessions, inject scripts, and send city credentials elsewhere. PORP lab practice puts research tools in a controlled, isolated environment after a basic trust review—not in the main Chrome used for occupancy licensing. Unsigned blog installs and loading the same add-ons onto database workstations expand the blast radius.