The Experts below are selected from a list of 116139 Experts worldwide ranked by ideXlab platform
Markus Schumacher - One of the best experts on this subject based on the ideXlab platform.
-
security Patterns integrating security and systems engineering
2006Co-Authors: Markus Schumacher, Duane Hybertson, Eduardo B Fernandez, Frank BuschmannAbstract:Chapter 1: The Pattern Approach. Patterns at a Glance. No Pattern is an Island. Patterns Everywhere. Humans are the Target. Patterns Resolve Problems and Shape Environments. Towards Pattern Languages. Documenting Patterns. A Brief Note on The History of Patterns. The Pattern Community and its Culture. Chapter 2: Security Foundations. Overview. Security Taxonomy. General Security Resources. Chapter 3: Security Patterns. The History of Security Patterns. Characteristics of Security Patterns. Why Security Patterns? Sources for Security Pattern Mining. Chapter 4: Patterns Scope and Enterprise Security. The Scope of Patterns in the Book. Organization Factors. Resulting Organization. Mapping to the Taxonomy. Organization in the Context of an Enterprise Framework. Chapter 5: The Security Pattern Landscape. Enterprise Security and Risk Management Patterns. Identification & Authentication (I&A) Patterns. Access Control Model Patterns. System Access Control Architecture Patterns. Operating System Access Control Patterns. Accounting Patterns. Firewall Architecture Patterns. Secure Internet Applications Patterns. Cryptographic Key Management Patterns. Related Security Pattern Repositories Patterns. Chapter 6: Enterprise Security and Risk Management. Security Needs Identification for Enterprise Assets. Asset Valuation. Threat Assessment. Vulnerability Assessment. Risk Determination. Enterprise Security Approaches. Enterprise Security Services. Enterprise Partner Communication. Chapter 7: Identification and Authentication (I&A). I&A Requirements. Automated I&A Design Alternatives. Password Design and Use. Biometrics Design Alternatives. Chapter 8: Access Control Models. Authorization. Role-Based Access Control. Multilevel Security. Reference Monitor. Role Rights Definition. Chapter 9: System Access Control Architecture. Access Control Requirements. Single Access Point. Check Point. Security Session. Full Access with Errors. Limited Access. Chapter 10: Operating System Access Control. Authenticator. Controlled Process Creator. Controlled Object Factory. Controlled Object Monitor. Controlled Virtual Address Space. Execution Domain. Controlled Execution Environment. File Authorization. Chapter 11: Accounting. Security Accounting Requirements. Audit Requirements. Audit Trails and Logging Requirements. Intrusion Detection Requirements. Non-Repudiation Requirements. Chapter 12: Firewall Architectures. Packet Filter Firewall. Proxy-Based Firewall. Stateful Firewall. Chapter 13: Secure Internet Applications. Information Obscurity. Secure Channels. Known Partners. Demilitarized Zone. Protection Reverse Proxy. Integration Reverse Proxy. Front Door. Chapter 14: Case Study: IP Telephony. IP Telephony at a Glance. The Fundamentals of IP Telephony. Vulnerabilities of IP Telephony Components. IP Telephony Use Cases. Securing IP telephony with Patterns. Applying Individual Security Patterns. Conclusion. Chapter 15: Supplementary Concepts. Security Principles and Security Patterns. Enhancing Security Patterns with Misuse Cases. Chapter 16: Closing Remarks. References. Index.
-
security engineering with Patterns
2003Co-Authors: Markus SchumacherAbstract:Conducting digital business requires secure network and application architectures. The recently increasing occurrence of severe attacks has shown, however, that we will still need quite some time and effort to reach security standards of IT systems alike the standard already usual in other fields. At present, there is a huge gap between theory and the code of practice. Whereas scientists work on formal approaches for the specification and verification of security requirements, practitioners have to meet the users requirements. The Pattern Community recognized this problem, too. Patterns literally capture the experience from experts in a structured way. Thus novices can benefit from know-how and skills of experts. Hence, we propose to apply the Pattern approach to the security problem. We show that recent security approaches are not sufficient and describe how Security Patterns contribute to the overall process of security engineering. A Security Pattern System provides linkage between Security Patterns. Thus dependencies between specific security problems can be considered in a comprehensive way.
Frank Buschmann - One of the best experts on this subject based on the ideXlab platform.
-
security Patterns integrating security and systems engineering
2006Co-Authors: Markus Schumacher, Duane Hybertson, Eduardo B Fernandez, Frank BuschmannAbstract:Chapter 1: The Pattern Approach. Patterns at a Glance. No Pattern is an Island. Patterns Everywhere. Humans are the Target. Patterns Resolve Problems and Shape Environments. Towards Pattern Languages. Documenting Patterns. A Brief Note on The History of Patterns. The Pattern Community and its Culture. Chapter 2: Security Foundations. Overview. Security Taxonomy. General Security Resources. Chapter 3: Security Patterns. The History of Security Patterns. Characteristics of Security Patterns. Why Security Patterns? Sources for Security Pattern Mining. Chapter 4: Patterns Scope and Enterprise Security. The Scope of Patterns in the Book. Organization Factors. Resulting Organization. Mapping to the Taxonomy. Organization in the Context of an Enterprise Framework. Chapter 5: The Security Pattern Landscape. Enterprise Security and Risk Management Patterns. Identification & Authentication (I&A) Patterns. Access Control Model Patterns. System Access Control Architecture Patterns. Operating System Access Control Patterns. Accounting Patterns. Firewall Architecture Patterns. Secure Internet Applications Patterns. Cryptographic Key Management Patterns. Related Security Pattern Repositories Patterns. Chapter 6: Enterprise Security and Risk Management. Security Needs Identification for Enterprise Assets. Asset Valuation. Threat Assessment. Vulnerability Assessment. Risk Determination. Enterprise Security Approaches. Enterprise Security Services. Enterprise Partner Communication. Chapter 7: Identification and Authentication (I&A). I&A Requirements. Automated I&A Design Alternatives. Password Design and Use. Biometrics Design Alternatives. Chapter 8: Access Control Models. Authorization. Role-Based Access Control. Multilevel Security. Reference Monitor. Role Rights Definition. Chapter 9: System Access Control Architecture. Access Control Requirements. Single Access Point. Check Point. Security Session. Full Access with Errors. Limited Access. Chapter 10: Operating System Access Control. Authenticator. Controlled Process Creator. Controlled Object Factory. Controlled Object Monitor. Controlled Virtual Address Space. Execution Domain. Controlled Execution Environment. File Authorization. Chapter 11: Accounting. Security Accounting Requirements. Audit Requirements. Audit Trails and Logging Requirements. Intrusion Detection Requirements. Non-Repudiation Requirements. Chapter 12: Firewall Architectures. Packet Filter Firewall. Proxy-Based Firewall. Stateful Firewall. Chapter 13: Secure Internet Applications. Information Obscurity. Secure Channels. Known Partners. Demilitarized Zone. Protection Reverse Proxy. Integration Reverse Proxy. Front Door. Chapter 14: Case Study: IP Telephony. IP Telephony at a Glance. The Fundamentals of IP Telephony. Vulnerabilities of IP Telephony Components. IP Telephony Use Cases. Securing IP telephony with Patterns. Applying Individual Security Patterns. Conclusion. Chapter 15: Supplementary Concepts. Security Principles and Security Patterns. Enhancing Security Patterns with Misuse Cases. Chapter 16: Closing Remarks. References. Index.
-
Pattern oriented software architecture a system of Patterns
1996Co-Authors: Frank BuschmannAbstract:Patterns. Architectural Patterns. Design Patterns. Idioms. Pattern Systems. Patterns and Software Architecture. The Pattern Community. Where Will Patterns Go? Notations. Glossary. References. Index of Patterns.
Hiroshi Nakano - One of the best experts on this subject based on the ideXlab platform.
-
from Pattern languages to a project language a shift proposal from existing Pattern Community
PLoP '13 Proceedings of the 20th Conference on Pattern Languages of Programs, 2013Co-Authors: Masanari Motohashi, Eiiti Hanyuda, Hiroshi NakanoAbstract:Patterns and Pattern languages are accepted worldwide and used in various areas of IT such as Design Patterns, Analysis Patterns, Domain Driven Developments, and AGILE SOFTWARE DEVELOPMENT. Although Patterns are successful in such areas, they are less accepted in the areas of large development and planning projects. We suggest that large projects and communities should be responsible for identifying and documenting their own Patterns instead of adopting those found in Pattern libraries. This is consistent with Alexander's hope to use Patterns and Pattern languages as part of his emphasis on planning and Community involvement. Our paper focuses on the beginnings of a Pattern language that we believe will facilitate the writing of appropriate Patterns for different situations by those involved in solving and building in those same situations. Additionally we propose "a Project Language" as a different form of Pattern Language, consisting of episodes and stories. In this paper, we have thus focus upon the essence of C. Alexander's Community Planning and a centering process via Pattern language. In this paper we argue for a turn from the existing dominant ideas a out how to use Patterns by professionals to a positive, Community-centric way participants to think about and act on their own Pattern languages. This new approach is, we believe, both urgent and indispensable at this time.
Masanari Motohashi - One of the best experts on this subject based on the ideXlab platform.
-
from Pattern languages to a project language a shift proposal from existing Pattern Community
PLoP '13 Proceedings of the 20th Conference on Pattern Languages of Programs, 2013Co-Authors: Masanari Motohashi, Eiiti Hanyuda, Hiroshi NakanoAbstract:Patterns and Pattern languages are accepted worldwide and used in various areas of IT such as Design Patterns, Analysis Patterns, Domain Driven Developments, and AGILE SOFTWARE DEVELOPMENT. Although Patterns are successful in such areas, they are less accepted in the areas of large development and planning projects. We suggest that large projects and communities should be responsible for identifying and documenting their own Patterns instead of adopting those found in Pattern libraries. This is consistent with Alexander's hope to use Patterns and Pattern languages as part of his emphasis on planning and Community involvement. Our paper focuses on the beginnings of a Pattern language that we believe will facilitate the writing of appropriate Patterns for different situations by those involved in solving and building in those same situations. Additionally we propose "a Project Language" as a different form of Pattern Language, consisting of episodes and stories. In this paper, we have thus focus upon the essence of C. Alexander's Community Planning and a centering process via Pattern language. In this paper we argue for a turn from the existing dominant ideas a out how to use Patterns by professionals to a positive, Community-centric way participants to think about and act on their own Pattern languages. This new approach is, we believe, both urgent and indispensable at this time.
Eiiti Hanyuda - One of the best experts on this subject based on the ideXlab platform.
-
from Pattern languages to a project language a shift proposal from existing Pattern Community
PLoP '13 Proceedings of the 20th Conference on Pattern Languages of Programs, 2013Co-Authors: Masanari Motohashi, Eiiti Hanyuda, Hiroshi NakanoAbstract:Patterns and Pattern languages are accepted worldwide and used in various areas of IT such as Design Patterns, Analysis Patterns, Domain Driven Developments, and AGILE SOFTWARE DEVELOPMENT. Although Patterns are successful in such areas, they are less accepted in the areas of large development and planning projects. We suggest that large projects and communities should be responsible for identifying and documenting their own Patterns instead of adopting those found in Pattern libraries. This is consistent with Alexander's hope to use Patterns and Pattern languages as part of his emphasis on planning and Community involvement. Our paper focuses on the beginnings of a Pattern language that we believe will facilitate the writing of appropriate Patterns for different situations by those involved in solving and building in those same situations. Additionally we propose "a Project Language" as a different form of Pattern Language, consisting of episodes and stories. In this paper, we have thus focus upon the essence of C. Alexander's Community Planning and a centering process via Pattern language. In this paper we argue for a turn from the existing dominant ideas a out how to use Patterns by professionals to a positive, Community-centric way participants to think about and act on their own Pattern languages. This new approach is, we believe, both urgent and indispensable at this time.