A method of associating applications with relativity metrics for later use in handling interprocess messages, said method comprising: receiving a first executable file for a first application; if said first executable file comprises a first cryptographic identifier, verifying said first cryptographic identifier using a first cryptographic key; if said first cryptographic identifier is successfully verified, associating, based on said verifying said first cryptographic identifier, said first application with a first relativity metric, wherein said first cryptographic key used to verify said first cryptographic identifier is associated with said first relativity metric; receiving a second executable file for a second application; if said second executable file comprises a second cryptographic identifier, verifying said second cryptographic identifier using a second cryptographic key; if said second cryptographic identifier is successfully verified, associating, based on said verifying said second cryptographic identifier, said second application with a second relativity metric, wherein said second cryptographic key used to verify said second cryptographic identifier is associated with said second relativity metric; receiving a message from an origin process, said origin process associated with said first application, wherein an operating system (402, 902) supports execution of said first application on a device; determining a destination process for said message, said destination process associated with said second application, wherein the operating system (402, 902) supports execution of said second application on the device; determining that said first relativity metric is associated with said origin process; determining that said second relativity metric is associated with said destination process; analyzing whether, based on said first relativity metric and said second relativity metric, messages from said origin process are allowed to be passed to said destination process; and passing said message to said destination process only if allowed based on said analyzing. receiving a first executable file for a first application; if said first executable file comprises a first cryptographic identifier, verifying said first cryptographic identifier using a first cryptographic key; if said first cryptographic identifier is successfully verified, associating, based on said verifying said first cryptographic identifier, said first application with a first relativity metric, wherein said first cryptographic key used to verify said first cryptographic identifier is associated with said first relativity metric; receiving a second executable file for a second application; if said second executable file comprises a second cryptographic identifier, verifying said second cryptographic identifier using a second cryptographic key; if said second cryptographic identifier is successfully verified, associating, based on said verifying said second cryptographic identifier, said second application with a second relativity metric, wherein said second cryptographic key used to verify said second cryptographic identifier is associated with said second relativity metric; receiving a message from an origin process, said origin process associated with said first application, wherein an operating system (402, 902) supports execution of said first application on a device; determining a destination process for said message, said destination process associated with said second application, wherein the operating system (402, 902) supports execution of said second application on the device; determining that said first relativity metric is associated with said origin process; determining that said second relativity metric is associated with said destination process; analyzing whether, based on said first relativity metric and said second relativity metric, messages from said origin process are allowed to be passed to said destination process; and passing said message to said destination process only if allowed based on said analyzing.