Refine
Departments, institutes and facilities
- Fachbereich Angewandte Naturwissenschaften (401)
- Institut für funktionale Gen-Analytik (IFGA) (381)
- Fachbereich Wirtschaftswissenschaften (344)
- Fachbereich Informatik (206)
- Fachbereich Elektrotechnik, Maschinenbau, Technikjournalismus (141)
- Fachbereich Sozialpolitik und Soziale Sicherung (114)
- Institut für Technik, Ressourcenschonung und Energieeffizienz (TREE) (106)
- Institut für Cyber Security & Privacy (ICSP) (51)
- Institute of Visual Computing (IVC) (48)
- Institut für Verbraucherinformatik (IVI) (45)
Document Type
- Article (1908) (remove)
Year of publication
Language
Keywords
- apoptosis (9)
- GC/MS (8)
- ISM: molecules (8)
- Malus domestica (8)
- Molecular dynamics (7)
- Qualitätsmanagement (7)
- Software (7)
- Mal d 1 (6)
- Virtual reality (6)
- Africa (5)
A qualitative study of Machine Learning practices and engineering challenges in Earth Observation
(2021)
Today’s computer systems face a vast array of severe threats that are posed by automated attacks performed by malicious software as well as manual attacks by individual humans. These attacks not only differ in their technical implementation but may also be location-dependent. Consequentially, it is necessary to join the information from heterogeneous and distributed attack sensors in order to acquire comprehensive information on current ongoing cyber attacks.
Malware is responsible for massive economic damage. Being the preferred tool for digital crime, botnets are becoming increasingly sophisticated, using more and more resilient, distributed infrastructures based on peer-to-peer (P2P) protocols. On the other side, current investigation techniques for malware and botnets on a technical level are time-consuming and highly complex. Fraunhofer FKIE is addressing this problem, researching new ways of intelligent process automation and information management for malware analysis in order to minimize the time needed to investigate these threats.
Routing Attacks are a serious threat to communication in tactical MANETs. TOGBAD is a centralised approach, using topology graphs to detect such attacks. In this paper, we present TOGBAD's newly added wormhole detection capability. It is an adaptation of a wormhole detection method developed by Hu et al. This method is based on nodes' positions. We adapted it to the specific properties of tactical environments. Furthermore, we present simulation results which show TOGBAD's performance regarding the detection of wormhole attacks.
Usable Security und Privacy
(2010)
Secondary use of health data has a vital role in improving and advancing medical knowledge. While digital health records offer scope for facilitating the flow of data to secondary uses, it remains essential that steps are taken to respect wishes of the patient regarding secondary usage, and to ensure the privacy of the patient during secondary use scenarios. Consent, together with depersonalisation and its related concepts of anonymisation, pseudonymisation, and data minimisation are key methods used to provide this protection. This paper gives an overview of technical, practical, legal, and ethical aspects of secondary data use and discusses their implementation in the multi-institutional @neurIST research project.
Cultivation of Miscanthus x giganteus L. (Mis) with annual harvest of biomass could provide an additional C source for farmers. To test the potential of Mis-C for immobilizing inorganic N from slurry or manure and as a C source for soil organic matter build-up in comparison to wheat (Triticum aestivum L.) straw (WS), a greenhouse experiment was performed. Pot experiments with ryegrass (Lolium perenne L.) were set up to investigate the N dynamics of two organic fertilisers based on Mis at Campus Klein-Altendorf, Germany. The two fertilisers, a mixture of cattle slurry and Mis as well as cattle manure from Mis-bedding material resulted in a slightly higher N immobilisation. Especially at the 1st and 2nd harvest, they were partly significantly different compared with the WS treatments. The fertilisers based on Mis resulted in a slightly higher microbial biomass C and microbial biomass N and thus can be identified as an additional C source to prevent nitrogen losses and for the build-up of soil organic matter (SOM) in the long-term.
Software developers build complex systems using plenty of third-party libraries. Documentation is key to understand and use the functionality provided via the libraries’ APIs. Therefore, functionality is the main focus of contemporary API documentation, while cross-cutting concerns such as security are almost never considered at all, especially when the API itself does not provide security features. Documentations of JavaScript libraries for use in web applications, e.g., do not specify how to add or adapt a Content Security Policy (CSP) to mitigate content injection attacks like Cross-Site Scripting (XSS). This is unfortunate, as security-relevant API documentation might have an influence on secure coding practices and prevailing major vulnerabilities such as XSS. For the first time, we study the effects of integrating security-relevant information in non-security API documentation. For this purpose, we took CSP as an exemplary study object and extended the official Google Maps JavaScript API documentation with security-relevant CSP information in three distinct manners. Then, we evaluated the usage of these variations in a between-group eye-tracking lab study involving N=49 participants. Our observations suggest: (1) Developers are focused on elements with code examples. They mostly skim the documentation while searching for a quick solution to their programming task. This finding gives further evidence to results of related studies. (2) The location where CSP-related code examples are placed in non-security API documentation significantly impacts the time it takes to find this security-relevant information. In particular, the study results showed that the proximity to functional-related code examples in documentation is a decisive factor. (3) Examples significantly help to produce secure CSP solutions. (4) Developers have additional information needs that our approach cannot meet.
Overall, our study contributes to a first understanding of the impact of security-relevant information in non-security API documentation on CSP implementation. Although further research is required, our findings emphasize that API producers should take responsibility for adequately documenting security aspects and thus supporting the sensibility and training of developers to implement secure systems. This responsibility also holds in seemingly non-security relevant contexts.
