Abstract: Examples relate to dynamically adjusting a model for a security operations center (“SOC”). As such, the examples disclosed herein enable constructing a customer storage model over a set of time periods for a customer based on a set of resources of the SOC, a storage distribution model received from the customer related to expected usage of the set of resources, and a threat landscape for the customer. The customer storage model may be revised for a second time period based on actual storage use of the customer during a first time period, and a projection of an amount of data to be consumed in the second time period based on the threat landscape. Allocation of the resources in the SOC may be revised for the second time period based on the revision to the customer storage model.

Abstract: Examples relate to dynamically adjusting a model for a security operations center (“SOC”). As such, the examples disclosed herein enable constructing a customer storage model over a set of time periods for a customer based on a set of resources of the SOC, a storage distribution model received from the customer related to expected usage of the set of resources, and a threat landscape for the customer. The customer storage model may be revised for a second time period based on actual storage use of the customer during a first time period, and a projection of an amount of data to be consumed in the second time period based on the threat landscape. Allocation of the resources in the SOC may be revised for the second time period based on the revision to the customer storage model.

Abstract: The suitability of a service provider for performing a task having a sensitivity level is gauged by using a trust level associated with the provider, in conjunction with the sensitivity level, to gauge whether or not to allocate the task to the service provider.

Abstract: The suitability of a service provider for performing a task having a sensitivity level is gauged by using a trust level associated with the provider, in conjunction with the sensitivity level, to gauge whether or not to allocate the task to the service provider.

Abstract: The invention relates to a method of authenticating a users ability to carry out a transaction.

Abstract: A method of managing profile information in a heterogeneous network of devices is described, including the steps of distributing a user profile among one or more devices in the form of a plurality of profile nodes and administrating read/write operations on the profile nodes according to a coherence protocol, the coherence protocol being adapted to dynamically allocate administrative rights over the profile nodes to the devices, and conditionally cache the profile nodes according to dynamically determined caching rights. Characteristics and/or changes in the structure of the network and/or the devices constituting the network can cause the profile to be dynamically replicated and distributed across the network so that specific profile information is coherent and accessible to corresponding devices in the network. The invention provides a means for securely storing profile data across a disparate network while ensuring coherence and secutiry.

Abstract: A computer system comprising a trust engine for determining a trust level associated with a computer node and a policy engine for setting access requirements to a personal profile, from the computer node, based upon the determined trust level of the computer node and respective sensitivity levels associated with sub-components of the personal profile.