Communication security Security measures
8.1.4 Mapping security measures to threats
The Yes in a table designate that a particular security threat is mitigated by a corresponding security measure. It is usually a combination of security measures which can mitigate certain threats e.g. both authentication and authorization. Table 35 and Table 36 show in which way each of the security threats and vulnerabilities discussed in section 8.1.2.1 is mitigated by the security measures described in section 8.1.3. This way, solutions to enable event security can be discussed in a technology independent way. The sections 8.1.5 and 0 describe how the necessary security measures can be realized in WS- and RESTful environments. Table 35: Mapping security measures to threats – part one Security Measure\Threat Data destruction Unauthorized creation of malicious subscriptions Unauthorized modification and corruption of data Authentication Yes Verify the identity of the entity attempting to delete data. Yes Ensure that only authenticated entities can create subscriptions. This is in particular important if subscriptions are possible using on behalf of. Yes Verify the identity of the entity attempting to modify data. Authorization Yes Ensure that only authorized entities can delete data. Yes Ensure that only authorized entities can create subscriptions. This is in particular important if subscriptions are possible using on behalf of. Yes Ensure that only authorized entities can modify data. 88 Copyright © 2010 Open Geospatial Consortium, Inc. Security Measure\Threat Data destruction Unauthorized creation of malicious subscriptions Unauthorized modification and corruption of data Non-repudiation Yes Provide a proof that certain operations related to data deletion actually happened e.g. secure log, notarization, signatures.... Yes Provide a proof that certain operation related to subscription creation actually happened e.g. secure log, notarization, signatures.... Yes Provide a proof that certain operation related to data modification and corruption actually happened e.g. secure log, notarization, signatures.... Data confidentiality No Encrypted data can be deleted. No Encryption is not applicable here. No Certain encryption algorithms allow modification of data without actually decrypting data. Data integrity Yes The Event Service can provide a proof that data or part of the data has been deleted e.g. storage, processing and transmission of data by applying certain cryptographic techniques. NA Integrity of subscriptions is ensured by authorization. Yes The Event Service can provide a proof that data or part of the data has been modified e.g. storage, processing and transmission of data by applying certain cryptographic techniques. Availability No No No Privacy No No NoParts
» OWS-7 Event Architecture Engineering Report
» Scope OWS-7 Event Architecture Engineering Report
» Document contributor contact points
» Revision history OWS-7 Event Architecture Engineering Report
» Future work OWS-7 Event Architecture Engineering Report
» Foreword OWS-7 Event Architecture Engineering Report
» Abbreviated terms OWS-7 Event Architecture Engineering Report
» Resource Class ResourceWithLifetime Class
» ResourceManager Interface ResourceTermination Interface
» AdHocEventChannel Class AggregationChannel Class
» EventChannel Class EventChannelRelationship Class
» EventMetadata Class EventingInformation Class
» Endpoint Class EndpointDeliveryMetadata Class
» Filter Class Notification Class
» PausableSubscription Class Producer Package
» Producer Class Publication Class
» Registration Class Broker Package
» Resources Lifecycle Management Behavior Model
» Managing Subscriptions Behavior Model
» Handling a Pausable Subscription
» Demand Based Publishing Behavior Model
» Introduction Event Channels OWS-7 Event Architecture Engineering Report
» Publish Subscribe Requirements OWS-7 Event Architecture Engineering Report
» Introduction Realization of Publish Subscribe
» Requirements Mapping for WS-Notification
» Summary Realization of Publish Subscribe
» Introduction Event Metadata Example
» The Event Service Discovery Model The Event Service Discovery extension package
» Scenario 1: Find a Service providing Sensor Data that supports Comparison Filters
» Step 2: Scenario 2: Find a Service providing Aviation Data in a specified Area
» Sample Event Service objects Discovery challenges:
» Denial of service Security threats and vulnerabilities
» Message replay Security threats and vulnerabilities
» Message modification Security threats and vulnerabilities
» Spoof of identity Security threats and vulnerabilities
» Intermediary network devices Security threats and vulnerabilities
» Trojan horse type of attacks
» Authorization or access control
» Data confidentiality Security measures
» Data integrity Security measures
» Communication security Security measures
» Mapping security measures to threats
» Threat Mitigation in WS- Environment
» Threat Mitigation in RESTful Environment
» Reliability OWS-7 Event Architecture Engineering Report
» Boolean Result for Filter Statement
» Event Wrapper Potential Pitfalls
» Resolve Content Given By Reference
» Reference System Transformation Potential Pitfalls
» Filter Encoding XPath Filter Processing Languages
» Event Pattern Markup Language
» Spatial Filtering via Bounding Box
» Spatial Filtering of Events Using Dynamic Filter Properties
» Discovery of filter functionality
» Specifying events OWS-7 Event Architecture Engineering Report
» Geosynchronization OWS-7 Event Architecture Engineering Report
» Dynamic Sensor Tracking and Notification Aviation
» Introduction OGC service specifications related to the Event Architecture
» Foreign standards and specifications related to the Event Architecture
» SWE Common AIXM Information models
» Introduction Document object model
» Spatially enabled Common Alert Protocol
» Code lists Common Alert Protocol
» Resource references Other features Interoperability
» Geosynchronization Common Alert Protocol
» Filtering CAP messages Common Alert Protocol
» EDXL-DE Common Alert Protocol
» WXXM Resource Requirements Package
» Consumer Requirements Package Publish Subscribe Requirements Package
» Registrar Requirements Package Information models
» Brokered Publish Subscribe Requirements Package Registering Broker Requirements Package
» Aggregation Channel Requirements Package
» Ad Hoc Channel Requirements Package
» Pausable Provider Requirements Package Demand Based Publication Requirements Package
» CSW-ebRIM Extension Package for Event Service Discovery
» Additional Sample Queries for Event Service Discovery
» XML Schema for Event Metadata
Show more