X.B. Bouwman
Please Note
5 records found
1
Positioned between computer science and the social sciences, this empirical dissertation combines large-scale measurements of threat data and attacker activity with interviews and analysis of market and community dynamics. It compares commercial providers, open sources, and volunteer sharing communities, showing how each captures different parts of the threat landscape.
The findings reveal substantial limits to common assumptions about CTI. Leading commercial providers offer largely non-overlapping data, while users often value curation and low false-positive rates more than broad coverage. Open sharing communities can identify unique threats, but scalable quality assurance may exclude the novelty they seek to uncover. Finally, many commercial indicators were published only after the associated attacker activity had ended, limiting their use for real-time detection. Together, these findings show why CTI needs to be evaluated not by promises or convenient technical metrics, but by the security and organizational outcomes it actually produces. ...
Positioned between computer science and the social sciences, this empirical dissertation combines large-scale measurements of threat data and attacker activity with interviews and analysis of market and community dynamics. It compares commercial providers, open sources, and volunteer sharing communities, showing how each captures different parts of the threat landscape.
The findings reveal substantial limits to common assumptions about CTI. Leading commercial providers offer largely non-overlapping data, while users often value curation and low false-positive rates more than broad coverage. Open sharing communities can identify unique threats, but scalable quality assurance may exclude the novelty they seek to uncover. Finally, many commercial indicators were published only after the associated attacker activity had ended, limiting their use for real-time detection. Together, these findings show why CTI needs to be evaluated not by promises or convenient technical metrics, but by the security and organizational outcomes it actually produces.
No One Drinks From the Firehose
How Organizations Filter and Prioritize Vulnerability Information
The number of published software vulnerabilities is increasing every year. How do organizations stay in control of their attack surface despite their limited staff resources? Prior work has analyzed the overall software vulnerability ecosystem as well as patching processes within organizations, but not how these two are connected.We investigate this missing link through semi-structured interviews with 22 organizations in critical infrastructure and government services. We analyze where in these organizations the responsibility is allocated to collect and triage information about software vulnerabilities, and find that none of our respondents is acquiring such information comprehensively, not even in a reduced and aggregated form like the National Vulnerability Database (NVD). This means that information on known vulnerabilities will be missed, even in critical infrastructure organizations. We observe that organizations apply implicit and explicit coping mechanisms to reduce their intake of vulnerability information, and identify three trade-offs in these strategies: independence, pro-activeness and formalization.Although our respondents' behavior is in conflict with the widely accepted security advice to collect comprehensive vulnerability information about active systems, no respondents recall having experienced a security incident that was associated with missing information on a known software vulnerability. This suggests that, given scarce resources, reducing the intake of vulnerability information by up to 95% can be considered a rational strategy. Our findings raise questions about the allocation of responsibility and accountability for finding vulnerable systems, as well as suggest changing expectations around collecting vulnerability information.
We also conducted 14 interviews with security professionals that use paid threat intelligence. We find that value in this market is understood differently than prior work on quality metrics has assumed. Poor coverage and small volume appear less of a problem to customers. They seem to be optimizing for the workflow of their scarce resource – analyst time – rather than for the detection of threats. Respondents evaluate TI mostly through informal processes and heuristics, rather than the quantitative metrics that research has proposed. ...
We also conducted 14 interviews with security professionals that use paid threat intelligence. We find that value in this market is understood differently than prior work on quality metrics has assumed. Poor coverage and small volume appear less of a problem to customers. They seem to be optimizing for the workflow of their scarce resource – analyst time – rather than for the detection of threats. Respondents evaluate TI mostly through informal processes and heuristics, rather than the quantitative metrics that research has proposed.