Abstract: A method for scanning object carriers using at least two microscope slide scanners includes a) loading a feed unit for microscope slides with a plurality of microscope slides, each of which is part of one of a plurality of sample series, b) transferring one microscope slide from the feed unit to every microscope slide scanner not loaded with a microscope slide, c) carrying out a scanning process for each loaded microscope slide scanner, d) transferring each scanned microscope slide from the microscope slide scanner to an intermediate storage rack, e) providing a data set for every scanning process for analysis, and f) transferring all microscope slides of a sample series from the intermediate storage rack to a final storage rack.

Abstract: A method for scanning microscope slides using a device with at least one feed unit for microscope slide holders, at least two microscope slide scanners, at least one depositing device, and at least one industrial robot, includes: a) loading the feed unit with at least one microscope slide holder, which holds at least one microscope slide, b) removing the microscope slide from the at least one microscope slide holder, c) inserting the removed microscope slide into one of the microscope slide scanners, d) removing the microscope slide from one of the microscope slide scanners, and e) depositing the microscope slide in the depositing device, wherein steps b) to e) are carried out by at least one industrial robot.

Abstract: Methods, systems, and computer-readable storage media for analyzing source code of an application. In some implementations, actions include determining, for at least one procedure invoked by the source code, a procedure specification specifying one or more conditions under which one or more parameters of the procedure are exploitable according to a parameter security specification; performing static application security testing on the source code by using the procedure specification on reaching an invocation of the procedure in the source code, including: comparing one or more invoking parameters of the invocation of the procedure to the conditions of the procedure specification; and determining whether the invocation of the procedure is exploitable.

Abstract: Methods, systems, and computer-readable storage media for analyzing source code of an application. In some implementations, actions include determining, for at least one procedure invoked by the source code, a procedure specification specifying one or more conditions under which one or more parameters of the procedure are exploitable according to a parameter security specification; performing static application security testing on the source code by using the procedure specification on reaching an invocation of the procedure in the source code, including: comparing one or more invoking parameters of the invocation of the procedure to the conditions of the procedure specification; and determining whether the invocation of the procedure is exploitable.

Abstract: Methods, systems, and computer-readable storage media for analyzing source code of an application. In some implementations, actions include determining a control flow graph of the application using the source code of the application; determining a plurality of source-sink pairs of exploitable data sources and exploitable data sinks; and determining, for each source-sink pair, whether the source-sink pair is potentially exploitable by: determining one or more conditions under which the invoking procedure passes the exploitable data source to the exploitable data sink of the invoked procedure; and determining, using the control flow graph, whether the conditions are met in at least one possible context of the application, and if so, determining that the source-sink pair is potentially exploitable.