An analyst is logged into a personal LinkedIn account while reviewing a vendor's public profile, and the vendor can see who viewed. What should the researcher do?
Select an answer to reveal the explanation.
Short Explanation
Some platforms are nosy neighbors: they tell the target who peeked. Do not peek from a real-name city account. Use a research persona or a logged-out public view.
Full Explanation
If an analyst is logged into a personal LinkedIn account while reviewing a vendor’s public profile and the vendor can see who viewed, the researcher should switch to a research persona or a logged-out public view so the real civic identity is not leaked. Viewer notifications are an OPSEC hazard in municipal due diligence because they can tip a bidder that city staff are looking. Keeping the personal account because view notifications are “never real” fails; many accounts do receive view signals or analytics, and assuming otherwise risks operational surprise. Friending the vendor from the personal account to unlock fields fails by expanding exposure, mixing personal network with civic research, and creating a lasting connection artifact. Emailing the vendor from the city domain to ignore the profile view fails as an awkward disclosure that confirms city interest without repairing the OPSEC error. Exam caveat: logged-out or persona views may show less data; that limitation is acceptable compared with leaking staff identity into a vendor’s viewer list. Operational check: use a dedicated research browser profile or approved sock hygiene; confirm logged-out or persona view before revisiting; note in the case file that personal viewing was discontinued and why.