hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 11.2.1 TTCN-3 messages decoding helpers | This class provides some helpers methods to decode messages into adapter internal data structures. Encoding rules and examples are shown in clause 6.2.2.3. Note that the Codec for encoding configuration TTCN-3 messages like GeneralConfigurationReq or decoding messages like GeneralConfigurationRsp in the TTCN-3 TE are d... |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 11.2.2 Socket implementation | The communication between the Adapter and the TrafficCapture processes uses a POSIX socket implementation. The class Socket provides a common implementation for all Adapter development. |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 11.2.3 Log framework | It provides a set of method for trace warning/error messages. It supports also trace levels (ERROR, INFO and DEBUG). |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 11.2.4 BOOST framework | Boost is a free library which is aimed at providing quality software components to developers, whilst using the styles of the Standard Template Library. Some of the components within the library may be put forward as future extensions to the Standard Library. Please refer to the BOOST references in [i.1] for a full doc... |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 11.2.5 Common development rules | This clause provides a list of common usage in the Adapter development process: • All the code shall be properly documented (principles, classes, methods, declarations, etc.). • 'Doxygen' style comments are used for code documentation. • For threading, boost with static method has been selected over class thread. |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 12 Implementation details | This clause introduces some development details of the different Adapter software components. |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 12.1 TTCN-3 messages execution | This clause shows the different implementations of the TTCN-3 messages supported by TTCN-3 components EutTrigger and EutConfiguration. |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 12.1.1 Automate equipment operation | This automation of equipment operation commands is vendor specific. However, a basic component, quickly customizable for each vendor, could be developed and integrated into the current software architecture. |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 12.1.2 Human friendly GUI | This kind of implementation is used when there is no way to automate equipment operation. In this case, equipment operation commands and parameters are presented by a graphical application to guide the user to achieve them. The messages to be displayed are stored in an XML file, one message per operation. This file can... |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 12.2 Class diagrams | Figure 19 describes the static architecture of the upper test adapter. It manages the equipment operation message port. Figure 19: Class diagram of the upper test adapter |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 12.3 Human friendly GUI | The human friendly GUI application is a component of the system adapter. It provides configurable messages/actions to guide the user to process actions or configure equipments. The messages/actions are displayed according to trigger messages received from the system adapter. The human friendly GUI application must be s... |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 12.4 TrafficCapture component | TrafficCapture is a component of the system adapter which takes care of capturing traffic from a network adapter. For correct functionality, it requires a pcap driver to be installed. It works as a standalone process communicating with the LowerTest component using the TCP/IP protocol. In this communication, TrafficCap... |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 12.4.1 Usage | When launched, the application starts listening on a specified port and waits for a connection attempt from the LowerTest component. The port number can be specified by the -p command line argument. If no port number is supplied this way, TrafficCapture uses port 5501. After LowerTest becomes connected, it sends severa... |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 12.4.2 Architecture | The core object of the application is a singleton TcpipServer instance. This instance opens a listening socket and accepts incoming connections. For all established connections, a separate ConnectionController is created. The controller object runs in an own thread and processes incoming messages from the client. It pa... |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 12.4.3 Functional Specification | All messages used in the communication with LowerTest are displayed in figure 21. This sequence diagram displays a typical scenario for a whole capture session. Individual use cases are described in detail in the following clauses. Figure 21: Sequence diagram of typical TrafficCapture session ETSI ETSI TR 101 561 V1.1.... |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 12.4.3.1 UC 01: File Merging | Precondition TCP/IP connection established. Description LowerTest sends a request (MergePcapFilesRequest) to merge two or more pcap files. TrafficCapture performs the operation, using an external tool - mergecap from the Wireshark package and send the result back to LowerTest (MergePcapFilesReply message). Success Merg... |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 12.4.3.2 UC 02: Opening Device | Precondition TCP/IP connection established In case of offline approach using multiple files, the files must be merged (clause 12.4.3.2) Description LowerTest sends a request (OpenDeviceRequest) to prepare a capturing device. TrafficCapture creates the device using a factory approach and initialises it. The of operation... |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 12.4.3.3 UC 03: Setting Filter | Precondition Capturing device ready (clause 12.4.3.2). Description LowerTest sends a request (SetFilterRequest) to set a filter for the capturing device. TrafficCapture applies the filter to the device overwriting the previous filter and sends back the operation result in a SetFilterReply message. Success Filter applie... |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 12.4.3.4 UC 04: Starting Capture | Precondition Capturing device ready (clause 12.4.3.2). Description LowerTest sends a request (StartCaptureRequest) to start capture. TrafficCapture replies with StartCaptureReply and starts sending CapturedData indication messages to LowerTest. These messages contain captured frames. Success Captured packets are being ... |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 12.4.3.5 UC 05: Stopping Capture | Precondition Packet capture started (clause 12.4.3.4). Description LowerTest sends a request (StopCaptureRequest) to stop frame capture. TrafficCapture stops sending CaptureData indications and replies with StopCaptureReply. Success Captured frames are no longer sent to LowerTest. Notice that the capturing device is st... |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 12.4.4 Compilation | The application is written in C++. It can be compiled with VisualStudio or gcc (tested with cygwin and MinGW version). The application uses two external libraries: pcap and boost. In case of compilation for Windows platform, Winsock 2 library is required as well. |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 13 Test case suite for Codec: the torture tests | In the case of an encoder input data is controlled and cannot go beyond the TTCN-3 typing possibilities. The decoder however can receive a huge variety of encoded messages. Therefore it is essential to ensure that the decoder will be robust enough to deal with these messages and to decode them. To achieve this goal, th... |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 13.1 Test System Architecture | These tests rely on the injection by the SUT adapter of encoded messages based on the testcase name and on timing after TriMap() call. Figure 22: Architecture ETSI ETSI TR 101 561 V1.1.1 (2011-06) 37 bool SipTorturePort::Map (const PortId& connected_port_id) { string filename ("data/"); filename += GetTestcaseId().GetO... |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 14 Testing of Test Adapter | In order to validate the Adapter functionalities and to provide a tool for regression tests, the adapter development provides a test suite named TestExecution, written in TTCN-3. This test suite covers the following functionalities: • Merge PCAP file tests. • General configuration message processing, including on-line ... |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 15 SVN repositories | The test adapter sources were archived into the STF407 project's SVN repositories and are attached to the present document in tr_101561v010101p0.zip. |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 16 Development tools | The adapter project uses the external libraries described below: • BOOST: two versions are used: - The version provided by CYGWIN (boost-1_33_1). It is used by the t3devkit toolkit. For more details, please refer to the installation procedure. - The latest version (currently boost_1_39_0), located here: http://www.boos... |
61e1809f923b58827f1864b3b2cc5e46 | 101 561 | 17 RFCs covered by the codec | The codec should be able to encode and decode all SIP messages supported by the TTCN-3 SIP library type structure. Therefore it should cover the message formats described in the following RFCs: • RFC 3261 [i.9] • RFC 3262 [i.10] • RFC 3265 [i.11] • RFC 3313 [i.12] • RFC 3323 [i.13] • RFC 3325 [i.14] • RFC 3326 [i.15] •... |
fddac23e6d0365331f9010c3f54113fe | 101 583 | 1 Scope | The present document defines terminology and an ontology which together provide the basis for a common understanding of security testing techniques which can be used in testing communication products and systems. The terminology and ontology have been derived from latest research, but also current standards and best pr... |
fddac23e6d0365331f9010c3f54113fe | 101 583 | 2 References | |
fddac23e6d0365331f9010c3f54113fe | 101 583 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which ar... |
fddac23e6d0365331f9010c3f54113fe | 101 583 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. NOTE: While any hyperlinks in... |
fddac23e6d0365331f9010c3f54113fe | 101 583 | 3 Definitions and abbreviations | |
fddac23e6d0365331f9010c3f54113fe | 101 583 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: asset: anything that has value to stakeholders, its business operation and its continuity (ETSI TS 102 165-1 [i.1]) attack: technique, process or script, malicious code or malware that can be launched to exploit a vulnerability or to b... |
fddac23e6d0365331f9010c3f54113fe | 101 583 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: CC Common Criteria CTMF Conformance Test Methodology and Framework DAST Dynamic Application Security Testing DDoS Distributed Denial of Service DoS Denial of Service MBST Model-Based Security Testing MBT Model-Based Testing SAST Static Applica... |
fddac23e6d0365331f9010c3f54113fe | 101 583 | 4 Introduction to security testing | In software engineering terms, security can be seen as an umbrella activity. The assessment of the security of a system is not a single, stand-alone activity but, rather, takes place at a number of different stages of the System or Software Development Lifecycle (SDLC). The purpose of security testing is to find weakne... |
fddac23e6d0365331f9010c3f54113fe | 101 583 | 5 Risk Assessment and Risk-based Security Testing | The security engineering process begins with the specification of security requirements. It typically involves an iterative security risk assessment that analyses the potential threats to a system in order to calculate the likelihood of their occurrence (IEEE St. 610.12-1990 [i.2]). The risk assessment comprises the id... |
fddac23e6d0365331f9010c3f54113fe | 101 583 | 6 Functional Testing of Security Features | Functional testing considers the system from the system functionality and functional requirements perspective. It comprises of unit, integration, product, system, interoperability and conformance testing. Functional security testing adopts the same approach but, in addition to benign, legitimate users, functional secur... |
fddac23e6d0365331f9010c3f54113fe | 101 583 | 7 Performance Testing | Performance testing, also called stress testing or load testing, aims to verify that the SUT can tolerate required constant load of service requests, and that the SUT will perform according to the performance requirements, and will have adequate response time for valid requests even while under load-based attacks. In t... |
fddac23e6d0365331f9010c3f54113fe | 101 583 | 8 Robustness Testing | Robustness testing aims to test that the system can tolerate certain level of attacks, and function correctly after the attack. Often referred to as "Fuzzing", this is a form of testing where system inputs are randomly mutated or systematically modified in order to find security-related failures such as crashes, busy-l... |
fddac23e6d0365331f9010c3f54113fe | 101 583 | 9 Penetration Testing | Penetration testing is very strictly reserved term used in formal security audits, reviews and conformance for assessments conducted by professional accredited security experts. Software testers should use caution to use the term, or use the term susceptibility testing for the security reviews, scans and/or tests. In t... |
fddac23e6d0365331f9010c3f54113fe | 101 583 | 10 Model-based Security Testing | Most security testing practises are manual activities or tool driven processes. Functional security tests e.g. those for TVRA are checklist type verifications against functional requirements, and typically require security experts or consultants to be performed. Load, stress and performance tests are at best automated ... |
bd28b397d90ae09c9326d725e6e18150 | 101 582 | 1 Scope | The present document reports on the application of model-based security testing in different industrial domain. Relevant case studies and their results are described in terms of system under test, applied tool chain, together with an overview of the technical requirements. The case studies were conducted as part of ITE... |
bd28b397d90ae09c9326d725e6e18150 | 101 582 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
bd28b397d90ae09c9326d725e6e18150 | 101 582 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. Not applicable. |
bd28b397d90ae09c9326d725e6e18150 | 101 582 | 2.2 Informative references | The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] AVANTSSAR Deliverable 2.3 (update): "ASLan++ specification and tutorial", 2011. NOTE: Available at http://www.avantssar.eu. [i.2] ITEA2 DIAMONDS Delive... |
bd28b397d90ae09c9326d725e6e18150 | 101 582 | 3 Definitions and abbreviations | |
bd28b397d90ae09c9326d725e6e18150 | 101 582 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: asset: anything that has value to the stakeholders (adopted from [i.15]) behavioural fuzzing: security testing technique that creates test procedures by changing a pre-known valid sequence of messages to an invalid sequence by rearrang... |
bd28b397d90ae09c9326d725e6e18150 | 101 582 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: AAT Abstract Attack Traces AP Access Point API Application Program Interface ATM Asynchronous Transfer Mode BAM Business Activity Monitoring BWCS Business Worst Case Scenario CAN Controller Area Network CSRF Cross-Site Request Forgery DBMS Dat... |
bd28b397d90ae09c9326d725e6e18150 | 101 582 | 4 Overview on case studies | The present document will provide an overview of the case studies and the final test results from the DIAMONDS project and the SPaCIoS project. DIAMONDS: The security of a software-intensive system is directly related to the quality of its software? In particular, over 90 % of software security incidents are caused by ... |
bd28b397d90ae09c9326d725e6e18150 | 101 582 | 5 Banknote processing case study results | |
bd28b397d90ae09c9326d725e6e18150 | 101 582 | 5.1 Case study characterization | This clause provides the revised case study description and requirements from the Giesecke & Devrient case study in the banking sector. It presents the applied security testing approaches as well as results achieved. The case study consists of a banknote processing system that counts and sorts banknotes depending on th... |
bd28b397d90ae09c9326d725e6e18150 | 101 582 | 5.1.1 Background | Banknote processing machines are used in central, large and medium banks and also in CITs (cash in transport) and other organizations that handle large amounts of banknotes. These machines are usually configured to work in a network as shown in figure 1. Currency processors, reconciliation stations, vault management sy... |
bd28b397d90ae09c9326d725e6e18150 | 101 582 | 5.1.2 System under test | While the banknote processing system consists of several components as depicted in figure 1, the focus of security tests is on the currency processor and the reconciliation station. The currency processor as well as the reconciliation station were provided as virtual machines, where external interfaces are replaced by ... |
bd28b397d90ae09c9326d725e6e18150 | 101 582 | 5.1.3 Security risk assessment | The currency processor is exposed to threats which compromise the accounting accuracy. The following high level treatments against the threats were identified: • Restricted access to functions: The access to security functions is restricted to authorized users. • Operation system access restriction: The access to the o... |
bd28b397d90ae09c9326d725e6e18150 | 101 582 | 5.2 Security testing approaches | As a result of the security risk assessment, several vulnerabilities were considered that should be tested whether they actually exists within the SUT. In order to generate appropriate tests for these vulnerabilities, security test patterns provide a suitable way to select test generation techniques or test procedures.... |
bd28b397d90ae09c9326d725e6e18150 | 101 582 | 5.2.1 Detection of vulnerability to injection attacks | The security test pattern is described by table 1a. ETSI ETSI TR 101 582 V1.1.1 (2014-06) 16 Table 1a: Test Pattern "Detection of Vulnerability to Injection Attacks" Pattern name Detection of Vulnerability to Injection Attacks Context Test pattern kind: Data Testing Approach(es): Prevention Problem/Goal Injection attac... |
bd28b397d90ae09c9326d725e6e18150 | 101 582 | 5.2.1.1 Data Fuzzing with TTCN-3 | In order to test for the above mentioned vulnerabilities identified during security risk assessment, both well established and new developed methods were applied to the system. Data fuzzing approaches for SQL injection were applied by a new developed fuzz testing extension for TTCN-3. Data fuzzing sends a large number ... |
bd28b397d90ae09c9326d725e6e18150 | 101 582 | 5.2.1.2 TTCN-3 | In order to be able to apply this method with TTCN-3, there was a need to extend the standardized language to support fuzz testing. Generally, matching mechanisms are used to replace values of single template fields or to replace even the entire contents of a template. Matching mechanisms may also be used in-line. A ne... |
bd28b397d90ae09c9326d725e6e18150 | 101 582 | 5.2.1.3 Data Fuzzing Library | In order to retrieve a valuable set of fuzzed values, a fuzzing library was implemented. It provides fuzz testing values from well-established fuzzers. These tools work standalone and thus, cannot be integrated in the existing test execution environment. So the fuzzing library was developed which allows integration in ... |
bd28b397d90ae09c9326d725e6e18150 | 101 582 | 5.2.2 Usage of unusual behaviour sequences | The vulnerability from the security risk assessment "Messages are executed without checking authentication" constitutes a message sequence that is unusual with respect to normal use of the SUT. Therefore, the security test pattern "Usage of Unusual Behaviour Sequences" is an appropriate starting point for generating te... |
bd28b397d90ae09c9326d725e6e18150 | 101 582 | 5.2.2.1 Behavioural fuzzing of UML sequence diagrams | A new fuzzing approach was developed for testing against the vulnerability of an authentication bypass. It consists of creating invalid message sequences instead of invalid input data by modifying functional test cases. While existing fuzzing approaches focus on data generation, a few approaches also implicitly or expl... |
bd28b397d90ae09c9326d725e6e18150 | 101 582 | 5.2.2.2 Online model-based behavioural fuzzing | Execution of a single test case takes very long time due to start-up times of the virtual machines and initializing them with a snapshot in order to achieve a consistent state. This step takes several minutes. Because fuzzing approaches generally result in a large number of test cases, this is a serious impediment. To ... |
bd28b397d90ae09c9326d725e6e18150 | 101 582 | 5.3 Results | |
bd28b397d90ae09c9326d725e6e18150 | 101 582 | 5.3.1 Requirements coverage | The existing TTCN-3 framework including their test adapters were customized for the test development and execution tool. This was necessary because of subtle differences in the interpretation of the TTCN-3 specification by the different TTCN-3 test execution environments. For this step, test adapters were reused and ad... |
bd28b397d90ae09c9326d725e6e18150 | 101 582 | 5.3.2 Test results | Based on the risk models, 30 behavioural fuzz test cases were executed on the SUT regarding an authentication bypass. Additionally, an initial set of 24 test cases using SQL injection to bypass the authentication were executed. No security- related issues were found. Considering the domain of the case study, banking, t... |
bd28b397d90ae09c9326d725e6e18150 | 101 582 | 5.4 Summary and conclusion | Starting the security tests with the development of a risk model to visualize and discuss the vulnerabilities, threats and consequences has proved useful and will be adopted by the standard development process. The applied fuzzing approaches allow reusing of existing, functional test cases to test the non-functional se... |
bd28b397d90ae09c9326d725e6e18150 | 101 582 | 6 Banking case study results | |
bd28b397d90ae09c9326d725e6e18150 | 101 582 | 6.1 Case study characterization | The aim of the Accurate Equity (formerly known as Norse Solutions) case study was to evaluate a process which combines security risk assessment and security testing when applied to the Norse Options web-portal (which is the software that Accurate Equity provides to its customers). In the case study, Accurate Equity pla... |
bd28b397d90ae09c9326d725e6e18150 | 101 582 | 6.2 Security testing approaches | In this clause, an overview is given of the process for test-based security risk assessment that was followed in the Accurate Equity case study. For a more a description of the current version of this process, see DIAMONDS deliverable D5.WP4 [i.4]. ETSI ETSI TR 101 582 V1.1.1 (2014-06) 27 Security Risk Analysis Securit... |
bd28b397d90ae09c9326d725e6e18150 | 101 582 | 6.3 Results | The objective of the evaluation is was assess how useful testing is for gaining confidence in the correctness the risk models produced in the security risk assessment (phase 1 above). To make the evaluation precise, the focus was specifically on the degree to which the testing yielded information that caused us to chan... |
bd28b397d90ae09c9326d725e6e18150 | 101 582 | 6.4 Summary and conclusion | The partners involved in the case study have gained important practical experience in applying a process which combines security risk assessment and testing. As a result of the case study, Accurate Equity has increased its awareness about security in their application, and will continue to use security risk assessment ... |
bd28b397d90ae09c9326d725e6e18150 | 101 582 | 7 Radio case study results | |
bd28b397d90ae09c9326d725e6e18150 | 101 582 | 7.1 Case study characterization | |
bd28b397d90ae09c9326d725e6e18150 | 101 582 | 7.1.1 Context of Mobile ad-hoc networks | The Radio Protocol Case study is based on ad hoc Radio Network. These protocols cover the following particularities: • Decentralized mesh network. No Base Station: One major challenge of these networks is to be independent to any infrastructure between the network units. Each node (also called radio unit) has the capab... |
bd28b397d90ae09c9326d725e6e18150 | 101 582 | 7.1.2 Status of the test of security testing at the beginning of the project | Until recently, the security analysis of such radio equipment were mainly delegated on communication ciphering components of the application, dependent on particular values (seeds, keys) manually injected by the user for a specific mission. These security protections are still used for the protection against threats an... |
bd28b397d90ae09c9326d725e6e18150 | 101 582 | 7.1.3 Security testing capabilities targeted | This clause summarizes the list of security testing analysis targeted to be validated at the end of the DIAMONDS project. As shown in figure 17, the scope of vulnerability analysis is focused on Packet Data Units messages transmitted over the air between pair nodes. The information of the messages (and potential threat... |
bd28b397d90ae09c9326d725e6e18150 | 101 582 | 7.1.3.1 Frames analysis | The on the fly or post analysis from an intrusive node offers the capability to an intrusive node to capture sequences of messages exchanged between peer entities; and: • to refine the understanding of the protocol behaviour and detect weaknesses for a second disturbance phase; • to collect the traffic information exch... |
bd28b397d90ae09c9326d725e6e18150 | 101 582 | 7.1.3.2 Data alteration | One potential threat is, for a node acquiring a more or less fine knowledge of the protocol of the data exchanged, to send a message instead of a node in the network, with a modified value of the data transmitted. This modification can be done in randomly modifying the value of fields in the data sent with respect to t... |
bd28b397d90ae09c9326d725e6e18150 | 101 582 | 7.1.3.3 Frames replay | Another threat situation, as described in figure 20 is to record a particular sequence of messages between two nodes, with or without modification of this sequence of messages. Figure 20: Frames replay Example on the radio protocol: The request and suppression of allocation dedicated to a particular node can be replaye... |
bd28b397d90ae09c9326d725e6e18150 | 101 582 | 7.1.3.4 Denial of service | The particular situation of the denial of service is the interaction in the communication between peer entities. The intruder node replaces one of the two peer node is acknowledging at its place always positively or negatively, in function of the disturbance expected. Figure 21: Denial of service Example on the radio p... |
bd28b397d90ae09c9326d725e6e18150 | 101 582 | 7.1.3.5 Tampering, malicious code injection | The following kind of threat is the injection of malicious code directly integrated in the protocol stack, for example resulting of a modifying load of new service Over The Air. Figure 22: Tampering, malicious code injection Example on the radio protocol: More accurate behaviour modification can be applied on this kind... |
bd28b397d90ae09c9326d725e6e18150 | 101 582 | 7.1.3.6 Combination of threats | The threats can be composed as a combination of the different situation described in the precedent clause. Figure 23: Combination of threats |
bd28b397d90ae09c9326d725e6e18150 | 101 582 | 7.1.4 Description of the use-case | The Open Systems Interconnection model (OSI model) shown in figure 24 is a product of the Open Systems Interconnection effort at the International Organization for Standardization. It is a way of sub-dividing a communications system into smaller parts called layers. A layer provides services to its upper layer while re... |
bd28b397d90ae09c9326d725e6e18150 | 101 582 | 7.1.4.1 Specific application used as Use Case | The application used as Use Case is a full designed OSI layered ad-hoc protocol application, from Physical to IP Convergence sub-layer application. • At physical layer: modulation and demodulation, management of the dwell level of the slots of the TDMA and definition of the slots of the TDMA. • At Medium Access Control... |
bd28b397d90ae09c9326d725e6e18150 | 101 582 | 7.1.4.2 Specific context of the application of security testing tools | The properties for security testing focused on the neighbourhood management. The management of the 1 and 2 hops neighbourhood detection is processed by a specific service in the MAC layer. This service initializes and updates from PDU exchanged: • One hop neighbours broadcast channels to emit control signal on lists ma... |
bd28b397d90ae09c9326d725e6e18150 | 101 582 | 7.1.4.3 Specific context of the initial validation framework | The initial validation framework used for the integration of the tool set was an event based simulation (as ns-3 or OMNET). The simulations execute the real C/C++ final encoding, and are used for a first functional validation, and validation of the protocol behaviour of a set of nodes interacting with each other. Scena... |
bd28b397d90ae09c9326d725e6e18150 | 101 582 | 7.2 Security testing approaches | |
bd28b397d90ae09c9326d725e6e18150 | 101 582 | 7.2.1 General principles of the security testing tools integration | The radio equipment design process, as shown in the following picture, validates at different stages the functional behavior of the radio protocol being designed. At each phase the validation validates requirements by simulation/execution on demonstrator of scenarios. The security testing approach is to integrate the s... |
bd28b397d90ae09c9326d725e6e18150 | 101 582 | 7.2.1.1 Verification framework adaptation | For each one of the process validation steps, the testing validation environment scheme may be abstracted as the left side picture below. Functional test are refined from the specification and executed from a scenario driver to the set of nodes simulated or executed. The DIAMONDS framework extension consists on the add... |
bd28b397d90ae09c9326d725e6e18150 | 101 582 | 7.2.1.2 Adaptation of the event driven simulation environment | Figure 27 shows in the green square the current simulation environment, which means the simulation of a set of "sane" nodes to validate functional behaviours. This initial environment is adapted in order to integrate the following features. • A set of security testing properties to be defined from a vulnerability analy... |
bd28b397d90ae09c9326d725e6e18150 | 101 582 | 7.2.2 Properties validated | 19 properties have been specified, implemented and validated, a summary of the description of these properties. Security Rule 1 If one node receives two successive MSG_SPHY_DATA_IND messages from the same source, then these two messages have to be separated by 50 slots (two nodes with close enough to see each other wit... |
bd28b397d90ae09c9326d725e6e18150 | 101 582 | 7.2.3 Active testing | 7 threats have been specified, implemented and applied on scenarios, a summary of the description of these threats. Threat 1 The PDU of the spy node take exactly the same values as another received PDU (specially the mac address) and sent over the air with a wrong timeslot. Threat 2 The address and broadcast channel of... |
bd28b397d90ae09c9326d725e6e18150 | 101 582 | 7.3 Results | As shown in the previous clauses of the present document, the process followed by the contributors of the Test for security related to the Radio protocol use case was based on requirements about security testing features. These requirements identification was the first activity step. For the next step, the following ac... |
bd28b397d90ae09c9326d725e6e18150 | 101 582 | 7.4 Summary and conclusion | As show in the previous clauses, the test for security framework was integrated into the THALES Communications & Security execution platform into a real size protocol design (several dozen thousands of lines), with complicate Packet Data Units formats including correlations between messages (slots allocations behaviour... |
bd28b397d90ae09c9326d725e6e18150 | 101 582 | 8 Automotive case study results | |
bd28b397d90ae09c9326d725e6e18150 | 101 582 | 8.1 Case study characterization | As Information and Communication Technology (ICT) systems become more and more part of daily lives, current and future vehicles are more and more integrated into ICT networks. The consumer's smartphones, multimedia devices etc. are linked to the vehicles and allow the drivers or passengers to use the internet, to acces... |
bd28b397d90ae09c9326d725e6e18150 | 101 582 | 8.2 Security testing approaches | In this case study four different testing techniques have been applied. All of these techniques are described in work package 2 in more detail. An overview and the adaption are described below. |
bd28b397d90ae09c9326d725e6e18150 | 101 582 | 8.2.1 Security risk assessment | Similar to other case studies a security risk assessment has been done. This analysis was done with support of the CORAS approach. For that purpose an analysis with seven different threat scenarios were created. All of these threat scenarios have been analysed and classified with values for vulnerability, likelihood, a... |
bd28b397d90ae09c9326d725e6e18150 | 101 582 | 8.2.2 Fuzzing | Fuzzing is a technique that injects invalid or random input data in order to reveal vulnerabilities or unexpected behaviour by processing this data. How this input data is generated depends on the data format. Fuzz data generators specific for certain data formats are generally more successful in finding vulnerabilitie... |
bd28b397d90ae09c9326d725e6e18150 | 101 582 | 8.2.3 IOSTS-based passive testing approach | Figure 33 shows the framework of the symbolic passive testing approach. In this approach, the passive testing is performed by integration of two techniques: Symbolic execution and Parametric Trace Slicing. Based on the system specification or requirements the behaviour/attack scenario is identified for the Bluetooth pr... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.