Several security mechanisms such as digital signature, timestamp audits and trails, encryption, throttling, filtering, protect secrets etc. are available. These security mechanisms are not completely able to stop malicious attacks. For malicious hackers and attackers it is comparatively easy to exploit security loopholes at the user's end side. Behind such type of problem the main reason is bad software design and its implementation without proper risk analysis and mitigation. So, an idea to model availability states an Availability State Transition Model (ASTM) has been proposed in this article. In ASTM methodology, only design level details is required which can be easily retrieved from the software's design.
%0 Journal Article
%1 chandra2011availability
%A Chandra, Shalini
%A Khan, Raees Ahmad
%C New York, NY, USA
%D 2011
%I ACM
%J SIGSOFT Softw. Eng. Notes
%K availability dependability fault modeling performance
%N 3
%P 1--3
%R 10.1145/1968587.1968603
%T Availability State Transition Model
%U http://doi.acm.org/10.1145/1968587.1968603
%V 36
%X Several security mechanisms such as digital signature, timestamp audits and trails, encryption, throttling, filtering, protect secrets etc. are available. These security mechanisms are not completely able to stop malicious attacks. For malicious hackers and attackers it is comparatively easy to exploit security loopholes at the user's end side. Behind such type of problem the main reason is bad software design and its implementation without proper risk analysis and mitigation. So, an idea to model availability states an Availability State Transition Model (ASTM) has been proposed in this article. In ASTM methodology, only design level details is required which can be easily retrieved from the software's design.
@article{chandra2011availability,
abstract = {Several security mechanisms such as digital signature, timestamp audits and trails, encryption, throttling, filtering, protect secrets etc. are available. These security mechanisms are not completely able to stop malicious attacks. For malicious hackers and attackers it is comparatively easy to exploit security loopholes at the user's end side. Behind such type of problem the main reason is bad software design and its implementation without proper risk analysis and mitigation. So, an idea to model availability states an Availability State Transition Model (ASTM) has been proposed in this article. In ASTM methodology, only design level details is required which can be easily retrieved from the software's design.},
acmid = {1968603},
added-at = {2014-08-21T15:25:03.000+0200},
address = {New York, NY, USA},
author = {Chandra, Shalini and Khan, Raees Ahmad},
biburl = {https://www.bibsonomy.org/bibtex/2a00e3238e5f250e7310e2f1d8d3567b6/avail_map_stud},
description = {Availability state transition model},
doi = {10.1145/1968587.1968603},
interhash = {f10b13c7c5743bd34ff5e50e6d2220a6},
intrahash = {a00e3238e5f250e7310e2f1d8d3567b6},
issn = {0163-5948},
issue_date = {May 2011},
journal = {SIGSOFT Softw. Eng. Notes},
keywords = {availability dependability fault modeling performance},
month = may,
number = 3,
numpages = {3},
pages = {1--3},
publisher = {ACM},
timestamp = {2014-08-21T15:25:03.000+0200},
title = {Availability State Transition Model},
url = {http://doi.acm.org/10.1145/1968587.1968603},
volume = 36,
year = 2011
}