2003
DOI: 10.6028/nist.sp.800-55
|View full text |Cite
|
Sign up to set email alerts
|

Security metrics guide for information technology systems

Abstract: SP 800-55 is superseded in its entirety by the publication of SP 800-55 Revision 1

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
57
0
16

Year Published

2004
2004
2017
2017

Publication Types

Select...
5
4

Relationship

0
9

Authors

Journals

citations
Cited by 136 publications
(73 citation statements)
references
References 0 publications
0
57
0
16
Order By: Relevance
“…Za projektovanje i implementaciju ISMS u turističkim agencijama (TA) na raspolaganju su široko prihvaćeni međunarodni standardi najbolje prakse za: upravljanje rizikom; mere (kontrole) za smanjenje rizika na prihvatljiv nivo; opšte prihvaćene principe zaštite; sertifikaciju i akreditaciju ISMS; metrike zaštite; integraciju digitalne forenzike u sistem zaštite itd. [2, 3, 4, 5,6,7,8,14,15,16,19,20,21]. Kako implementacija ISMS generalno zahteva značajne resurse, u praksi se često zaštita informacija pojedostavljuje, improvizuje bez procene rizika i neadekvatno primenjuje što je možda i glavni razlog za optimizaciju, pošto se stvara iluzija o zaštiti, a istovremeno brojni gosti izlažu riziku online krađe brojeva platnih kartica i privatnih informacija iz lokalnih baza podataka TA.…”
Section: Uvodunclassified
“…Za projektovanje i implementaciju ISMS u turističkim agencijama (TA) na raspolaganju su široko prihvaćeni međunarodni standardi najbolje prakse za: upravljanje rizikom; mere (kontrole) za smanjenje rizika na prihvatljiv nivo; opšte prihvaćene principe zaštite; sertifikaciju i akreditaciju ISMS; metrike zaštite; integraciju digitalne forenzike u sistem zaštite itd. [2, 3, 4, 5,6,7,8,14,15,16,19,20,21]. Kako implementacija ISMS generalno zahteva značajne resurse, u praksi se često zaštita informacija pojedostavljuje, improvizuje bez procene rizika i neadekvatno primenjuje što je možda i glavni razlog za optimizaciju, pošto se stvara iluzija o zaštiti, a istovremeno brojni gosti izlažu riziku online krađe brojeva platnih kartica i privatnih informacija iz lokalnih baza podataka TA.…”
Section: Uvodunclassified
“…The often-used division into technical, operational and organizational security metrics (see e.g. [7] and [8]) does not sufficiently emphasize the technical system as a target. Most security metrics are needed during R&D, mainly by secure software developers and other personnel in the development project (viewpoints 1 and 2); and 3.…”
Section: Main Viewpoints On Targetmentioning
confidence: 99%
“…This provided an initial basis around which to organize taxonomy of security met-rics [6]. The U. S. National Institute of Information Standards and Technology (NIST) presents security metrics taxonomies in NIST Special Publication 800-26 [7] and 800-55 [8], suggesting the same three categories, and 17 sub-categories, mainly from an organizational perspective. In our SMOS model introduced in this article, technical metrics can be mapped to security-enforcing mechanisms and the security quality of system viewpoints, operational metrics to all three viewpoints, and organizational metrics to the secure lifecycle, project and business management viewpoint.…”
Section: Related Workmentioning
confidence: 99%
“…Most of them use security metrics to measure the situations. Such metrics are tools designed to facilitate decision making and improve performance and accountability through collection, analysis, and reporting of relevant performancerelated data [10]. IT security metrics monitor the accomplishment of the goals and objectives by quantifying the level of implementation of the security controls and the effectiveness and efficiency of the controls, analyzing the adequacy of security activities and identifying possible improvement actions.…”
Section: Literature Surveymentioning
confidence: 99%