A county recorder OSINT analyst stores investigation notes, screenshots, and research logins in the same browser profile used for personal online banking. What should the analyst change first?
Select an answer to reveal the explanation.
Short Explanation
Picture stuffing case files into the same wallet as a debit card. One lost bag, and banking cookies plus investigation artifacts walk out together. Civic OSINT needs a separate research profile so the personal cookie jar and the case cookie jar never mix.
Full Explanation
Personal and investigative browsing must be split into isolated profiles so banking cookies, personal sessions, and case artifacts never share a jar. A county recorder analyst who stores investigation notes, screenshots, and research logins in the same browser profile used for personal online banking creates contamination, credential risk, and potential exposure of civic research through personal account context. Keeping one profile so banking multifactor prompts can confirm the analyst during research visits is not a security design. Exporting the combined cookie jar to a shared drive so teammates inherit logged-in sessions spreads compromise. Turning off cookies on every city workstation so profile isolation is unnecessary is both impractical and orthogonal—isolation is still required for identity separation. Exam caveat: enterprise managed profiles can satisfy isolation if personal use is truly excluded from the research profile. Operational check: open a dedicated research profile or VM with no personal logins before the next recorder OSINT session, and verify the personal banking profile is not running in the same browser user data directory. Keep the civic purpose, method limits, and exhibit labels aligned so reviewers can see what was public-source work versus other authorities.