Why a security & compliance analyst should look beyond the incident
A scandal usually has a longer history than the moment it becomes public. That does not excuse an individual’s decision. It does make the conditions around that decision worth examining: what leaders rewarded, what teams learned to tolerate, and whether people expected concerns to be handled fairly. The aim is to understand how the organization’s systems and working culture shaped the conditions in which people acted.
The WSJ/Deloitte source reports that leadership influences ethical culture and that employees take cues from leaders. That makes leadership conduct relevant to an assessment, while leaving the circumstances and causes of any particular incident to be established through evidence.
What reporting data can—and cannot—tell you
Assess reporting confidence by separating three questions: Do employees know how to report? Do they believe they can report safely? Do they expect the organization to act? Policies and training records can help show whether procedures were communicated, but do not establish how employees feel or whether concerns receive appropriate follow-up.
To explore those questions, ask employees about confidentiality, protection from retaliation, and follow-up. Survey responses describe the views of respondents; their meaning depends on survey design and participation, and they do not establish what happened in a particular case. Review authorized case records separately for documented intake, triage, investigation, and corrective action. Those records may omit concerns that were never raised, and cannot by themselves explain why someone stayed silent. Together, these sources offer different evidence about reporting culture, not a complete picture.
How a security & compliance analyst can assess culture
Start by defining a risk area. Identify where employees may face pressure to meet targets, where exceptions are granted, and which roles may face professional or social costs for raising concerns. A focused scope gives the review a practical frame without implying that one review can capture an organization’s entire culture.
Match each method to the question it can answer. A survey can describe respondents’ perceptions. An audit can test selected requirements or procedures against the records and activities examined. Analytics can surface patterns in the data available for review; those patterns need context before they can support an interpretation. None of these methods alone establishes what happened in an individual case or why. These are assessment methods proposed here, not findings reported by the WSJ/Deloitte source.
Compare employee feedback with process records and investigation outcomes. If they conflict, preserve the discrepancy as a question for follow-up. For example, high reported awareness of a reporting channel alongside low recorded use could prompt a check of how awareness and use were measured, followed by questions about access and confidence. That contrast does not establish why concerns went unreported.
Trace a concern through the response process
Select a defined sample of authorized case records and reconstruct each case from intake to closure. Note what the documentation shows about receipt, triage, rationale, referral or investigation, and corrective action. Compare stages and handoffs where the records allow. The sample describes the cases selected; it cannot establish that they represent all concerns or reveal matters that were never recorded. Protect identifying information in analysis and reporting.
Where records permit, check whether receipt was acknowledged, whether the reporter was told how to provide more information, and whether follow-up was documented. A file marked “closed” establishes an administrative status in that record, not that the reporter understood the outcome or felt safe afterward. Be explicit about what the records cannot show rather than treating closure as evidence that the response was effective.
Treat gaps as leads for examination, not as proof of retaliation or inadequate corrective action. A conclusion that a process failed needs supporting evidence, such as documented delays, inconsistent handling, or a substantiated complaint. A conclusion that it worked also needs evidence. Keep observed facts, interpretations, and open questions distinct.
Keep technical evidence in its proper role
Use system logs for questions their contents and coverage can address, such as whether particular recorded access or changes occurred and when. Check which systems and events the logs cover; a log does not capture activity outside that scope. Logs can show recorded system activity, but cannot establish whether employees trust an ethics channel or believe leadership will respond fairly.
If a review concerns possible failure to escalate or concealment, preserve relevant authorized records, check their scope and integrity, and build a timeline of documented actions. Compare that timeline with applicable reporting and escalation procedures: who was expected to act, what information the records show was available, and whether required handoffs are documented. If responsibilities were unclear or recorded practice differed from policy, document the gap as a process issue to investigate rather than evidence of anyone’s motive.
Make findings measurable and useful
Tie each finding to a defined risk, the evidence supporting it, and a proposed change. If a selected case sample lacks recorded triage rationales, for example, propose documenting the rationale and responsible decision-maker. A later sample could measure the share of reviewed files containing that documentation. That measure describes documentation in the files reviewed; it does not measure whether employees feel safe reporting or whether every case was handled appropriately.
For each measure, state its numerator and denominator, time period, data source, and limits. Reporting volume alone cannot show whether trust improved: counts may change for several reasons and do not directly measure employee confidence. If you use reporting volume, interpret it alongside appropriately scoped employee feedback and evidence about case handling, and describe what remains uncertain.
Return to the concern that prompted the assessment. If records show inconsistent follow-up, specify which step should change and how a later case review would test whether documentation or handling changed. If employees report fear of retaliation, identify the protections they say they need and examine whether those protections are communicated and applied. Treat proposed changes as matters to test through follow-up, not guarantees that a remedy will work in every setting.
The analyst’s bottom line
Examine written rules, working processes, and employees’ reported experiences as distinct forms of evidence. When they conflict, document the gap and investigate what each source can and cannot establish. Keep conclusions within the available evidence, identify uncertainty, and revise them when better evidence emerges. For another perspective on the responsibilities of a security & compliance analyst, see why analysts should rethink AI moral surrender.
a security & compliance analyst should look beyond
Abstract editorial image in blue and teal, evoking ethical culture