A sheriff’s office exchanges Criminal Justice Information (CJI) with state systems and also runs a public website. How should channel security be matched to data sensitivity?
Select an answer to reveal the explanation.
Short Explanation
CJI is not a city blog post—you don’t wrap a evidence vault and a tourist brochure in the same thin wrapper. Give justice data stronger, policy-grade channels with approved crypto, mutual auth, and locked-down endpoints, and keep casual browsing separate. Same guest Wi-Fi rules, “TCP is TCP,” or turning TLS off for audits miss the sensitivity match.
Full Explanation
Secure communication design scales channel controls to the classification and regulatory obligations of the data. CJI exchanges typically require approved cryptographic protocols, stronger authentication, endpoint control, and monitoring beyond what is needed for public informational browsing. Equating CJI paths with guest Wi-Fi or anonymous web traffic understates confidentiality and integrity requirements. Disabling TLS to ease capture weakens the very protections audits are meant to verify.