| Literature DB >> 24563626 |
Abstract
Given the increasing cooperation between organizations, the flexible exchange of security information across the allied organizations is critical to effectively manage information systems (IS) security in a distributed environment. In this paper, we develop a cooperative model for IS security risk management in a distributed environment. In the proposed model, the exchange of security information among the interconnected IS under distributed environment is supported by Bayesian networks (BNs). In addition, for an organization's IS, a BN is utilized to represent its security environment and dynamically predict its security risk level, by which the security manager can select an optimal action to safeguard the firm's information resources. The actual case studied illustrates the cooperative model presented in this paper and how it can be exploited to manage the distributed IS security risk effectively.Entities:
Mesh:
Year: 2014 PMID: 24563626 PMCID: PMC3916018 DOI: 10.1155/2014/167497
Source DB: PubMed Journal: ScientificWorldJournal ISSN: 1537-744X
Figure 1Model architecture.
Figure 2Interactions among the components.
Information exchange in the interactive process.
| Exchange information | Description |
|---|---|
| Search request | It consists of the requester's id, IP address, and the required input variables. The estimation component has a set of sharing variables. To find components capable of providing required input data, the estimation component sends a search request to the registration component. |
| Search reply | It consists of the requested variable name, the IP address, and status of the component publishing the variable. Based on receiving a search request, the registration component searches its database to determine which components can provide the requested variables. |
| Registration message | It consists of component id, IP address, list of published variables, and their possible states. Each estimation component registers with the registration component, which issues an acknowledgment message for entering the new component in its database. |
| Communication between estimation components | It consists of the request id, the sender's id, and the probability distribution of the requested variable. Upon receiving the list of components capable of providing the required input from the registration component, the request component sends requests directly to these components. Then, the sender sends the probability distribution of the requested variable. |
Algorithm 1Bayesian network development algorithm.
BN information of M1.
| Node ID | Node name | State space | Parent nodes | Children nodes |
|---|---|---|---|---|
| M1_1 | Network access control | {Effective; average; ineffective} | Φ | {M1_7} |
| M1_2 | Network security audit | {Comprehensive; incomprehensive} | Φ | {M1_7} |
| M1_3 | Change management | {Effective; average; ineffective} | Φ | {M1_9} |
| M1_4 | Supplier threat level | {0; 1; 2; 3; 4; 5} | Φ | {M1_8} |
| M1_5 | Transporter threat level | {0; 1; 2; 3; 4; 5} | Φ | {M1_8} |
| M1_6 | Operational procedures and responsibilities | {Very standard; standard; non-standard} | Φ | {M1_9} |
| M1_7 | Network security | {High; medium; low} | {M1_1, M1_2} | {M1_10} |
| M1_8 | External systems security | {High; medium; low} | {M1_4, M1_5} | {M1_10} |
| M1_9 | Operation security | {High; medium; low} | {M1_3, M1_6} | {M1_10} |
| M1_10 | M1 threat level | {0; 1; 2; 3; 4; 5} | {M1_7, M1_8, M1_9} | Φ |
BN information of S1.
| Node ID | Node name | State space | Parent nodes | Children nodes |
|---|---|---|---|---|
| S1_1 | Communication secrecy | {High; medium; low} | Φ | {S1_6} |
| S1_2 | Audit logging | {Secure; average; insecure} | Φ | {S1_6} |
| S1_3 | Network access control | {Effective; average; ineffective} | Φ | {S1_5} |
| S1_4 | Network security audit | {Comprehensive; incomprehensive} | Φ | {S1_5} |
| S1_5 | Network security | {High; medium; low} | {S1_3, S1_4} | {S1_7} |
| S1_6 | Communication security | {High; medium; low} | {S1_1, S1_2} | {S1_7} |
| S1_7 | S1 threat level | {0; 1; 2; 3; 4; 5} | {S1_5, S1_6} | Φ |
Figure 3BN structures of M1 and S1.
Figure 4Security manager interface.