Abstract: A method for managing a first application program comprises: executing, by a first processor, a first control flow; executing, by a second processor, in synchronization with the first control flow execution, a second application, comprising a variable and an expected value that the variable has to have or a condition that the variable has to satisfy to authorize an execution of the correct first control flow; verifying, by the second processor, by executing each of the at least one second application, whether the variable has the expected value or the variable satisfies the condition; and inferring, by the second processor, if, for the second application, the variable has (not) the expected value or does (not) satisfy the condition, that the first processor is (not) executing the correct first control flow.

Abstract: The invention provides a method for verifying the state of a distributed ledger. This method comprises the steps of creating a chain of data blocks, performing an authentication writing operation in the chain of data blocks and checking the authentication time of the last authentication block. Each block comprises a signature which is based on information of the previous block. The authentication writing operation comprises authentication information voted by a plurality of trusted authentication nodes, creating at least one authentication block in an authentication time. The checking step is carried out by a software instance, thus considering the information of the distributed ledger as verified and alive until this authentication time.

Abstract: A method for managing a first application program comprises: executing, by a first processor, a first control flow; executing, by a second processor, in synchronization with the first control flow execution, a second application, comprising a variable and an expected value that the variable has to have or a condition that the variable has to satisfy to authorize an execution of the correct first control flow; verifying, by the second processor, by executing each of the at least one second application, whether the variable has the expected value or the variable satisfies the condition; and inferring, by the second processor, if, for the second application, the variable has (not) the expected value or does (not) satisfy the condition, that the first processor is (not) executing the correct first control flow.

Abstract: A method of obfuscating executable computer code to impede reverse-engineering, by interrupting the software's execution flow and replacing in-line code with calls to subroutines that do not represent logical program blocks. Embodiments of the present invention introduce decoy code to confuse attackers, and computed branching to relocated code so that actual program flow cannot be inferred from disassembled source representations.