Mažeika et al., 2020 - Google Patents
Integrating security requirements engineering into MBSE: Profile and guidelinesMažeika et al., 2020
View PDF- Document ID
- 1437781321688274287
- Author
- Mažeika D
- Butleris R
- Publication year
- Publication venue
- Security and Communication Networks
External Links
Snippet
Model‐Based System Engineering (MBSE) provides a number of ways on how to create, validate, and verify the complex system design; unfortunately, the inherent security aspects are addressed neither by the SysML language that is the main MBSE enabler nor by popular …
- 238000004891 communication 0 abstract description 17
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING; COUNTING
- G06F—ELECTRICAL DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
- G06F21/31—User authentication
- G06F21/34—User authentication involving the use of external additional devices, e.g. dongles or smart cards
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING; COUNTING
- G06F—ELECTRICAL DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/70—Protecting specific internal or peripheral components, in which the protection of a component leads to protection of the entire computer
- G06F21/71—Protecting specific internal or peripheral components, in which the protection of a component leads to protection of the entire computer to assure secure computing or processing of information
- G06F21/77—Protecting specific internal or peripheral components, in which the protection of a component leads to protection of the entire computer to assure secure computing or processing of information in smart cards
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING; COUNTING
- G06F—ELECTRICAL DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for programme control, e.g. control unit
- G06F9/06—Arrangements for programme control, e.g. control unit using stored programme, i.e. using internal store of processing equipment to receive and retain programme
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING; COUNTING
- G06F—ELECTRICAL DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING; COUNTING
- G06F—ELECTRICAL DIGITAL DATA PROCESSING
- G06F17/00—Digital computing or data processing equipment or methods, specially adapted for specific functions
- G06F17/20—Handling natural language data
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING; COUNTING
- G06F—ELECTRICAL DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING; COUNTING
- G06F—ELECTRICAL DIGITAL DATA PROCESSING
- G06F17/00—Digital computing or data processing equipment or methods, specially adapted for specific functions
- G06F17/30—Information retrieval; Database structures therefor; File system structures therefor
- G06F17/30286—Information retrieval; Database structures therefor; File system structures therefor in structured data stores
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING; COUNTING
- G06Q—DATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING; COUNTING
- G06F—ELECTRICAL DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING; COUNTING
- G06Q—DATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
Similar Documents
Publication | Publication Date | Title |
---|---|---|
Mažeika et al. | Integrating security requirements engineering into MBSE: Profile and guidelines | |
Ab Rahman et al. | Forensic-by-design framework for cyber-physical cloud systems | |
Mellado et al. | A systematic review of security requirements engineering | |
ben Othmane et al. | Extending the agile development process to develop acceptably secure software | |
El Kharbili et al. | Towards a framework for semantic business process compliance management | |
Li et al. | Security attack analysis using attack patterns | |
Mouratidis et al. | Security requirements engineering for cloud computing: The secure tropos approach | |
Matulevicius et al. | Syntactic and semantic extensions to secure tropos to support security risk management | |
Baca et al. | Countermeasure graphs for software security risk assessment: An action research | |
Papastergiou et al. | Handling of advanced persistent threats and complex incidents in healthcare, transportation and energy ICT infrastructures | |
Soomro et al. | Towards security risk-oriented misuse cases | |
Möller | NIST cybersecurity framework and MITRE cybersecurity criteria | |
Hudaib et al. | A survey on design methods for secure software development | |
Merkow et al. | Secure and resilient software: Requirements, test cases, and testing methods | |
Mazeika et al. | Identifying security issues with mbse while rebuilding legacy software systems | |
Fenz et al. | FORISK: Formalizing information security risk and compliance management | |
Kumar et al. | A quantitative security risk analysis framework for modelling and analyzing advanced persistent threats | |
Alrimawi et al. | Incidents are meant for learning, not repeating: sharing knowledge about security incidents in cyber-physical systems | |
Mažeika | Model-based systems engineering method for creating secure systems | |
Buvvaji et al. | Cybersecurity in the Age of Big Data: Implementing Robust Strategies for Organizational Protection | |
Larsen et al. | A Conceptual Model‐Based Systems Engineering Method for Creating Secure Cyber‐Physical Systems | |
Athinaiou et al. | Towards the definition of a security incident response modelling language | |
Khlevnoy et al. | A formal approach to distributed system security test generation | |
Wang et al. | Research on security requirements engineering process | |
Mellado et al. | Automated support for security requirements engineering in software product line domain engineering |