pm#process_supporting_the_security_of_some_RFID_related_network
  exclusion:  pm#process_supporting_the_security_of_some_RFID_tag  pm#process_supporting_the_security_of_some_RFID_reader  pm#process_supporting_the_security_of_some_RFID_related_application
  supertype:  pm#process_supporting_the_security_of_some_RFID_element
  object:  bridge#RFID_related_network [1..*,1..*] (pm)
  subtype:  bridge#process_supporting_authentication_in_some_RFID_related_network__id_req_net_1  Mutual authentication between the parties which takes part in EPC data communication. A large size scalable authentication infrastructure must be used.
     subtype:  bridge#process_authenticating_network_transactions_in_some_RFID_related_network__N17
     subtype:  bridge#process_authenticating_client_queries_in_some_RFID_related_network__NC2
     subtype:  bridge#process_ensuring_that_the_origin_of_event_in_an_RFID_related_network_is_provable__NI3
  subtype:  bridge#process_supporting_the_non-repudiation_of_information_in_some_RFID_related_network__id_req_net_5  Data contributions to the system must be signed in order that individual parties can me held accountable for the quality of the data they provide. There must be accountability for data validity (N19)
  subtype:  bridge#process_supporting_the_access_control_of_some_RFID_related_network__id_req_net_6  Information shares must own the capability to specify the conditions under which they want to share the data. These rules must be managed by sound access controls mechanism.
     subtype:  bridge#process_using_transport_security_to_complement_EPC_network_component_security__NI8___NC5
     subtype:  bridge#process_securing_event_collection_in_some_RFID_related_network__NC1
     subtype:  bridge#process_allowing_companies_to_choose_who_to_trust_with_hosted_data_in_some_RFID_related_network__processallowingcompaniestochoosewhototrustwithhosteddatainsomerfidrelatednetwork__NC3__nc3
     subtype:  bridge#process_allowing_companies_to_have_withdrawal_and_access_control_over_their_hosted_data_in_some_RFID_related_network__NC4
  subtype:  bridge#process_supporting_the_integrity_of_information_in/from_some_RFID_related_network
     subtype:  bridge#process_supporting_only_authorized_and_accurate_registration_of_EPC_ISs_in_a_DS__id_req_net_7a  Only authorized parties must be allowed to register their EPC ISs with a DS in such a way that parties can not be injected selfishly and inaccurate information into the system.
     subtype:  bridge#process_supporting_the_visibility_and_up-to_date_nature_of_information_in_some_RFID_related_network__id_req_net_7b  A client's access rights must be able to access 'all' the data she is entitled to. In order to prevent from data inconsistency the information must be up-to-date.
     subtype:  bridge#process_and__RFID_infrastructure_allowing_effective_anti-counterfeiting_through_multiparty_track_and_trace_information___NI2
     subtype:  bridge#process_allowing_only_secure_updates_to_prevent_data_corruption_in_RFID_related_network__NI4
     subtype:  bridge#process_making_trusted_parties_validate_received_data_in_RFID_related_network__NI5
     subtype:  bridge#process_ensuring_that_network_transactions_are_well_formed__NI6
  subtype:  bridge#process_supporting_the_confidentiality_of_communication_in_a_RFID_related_network__id_req_net_2  A scalable confidential architecture must be used. The external transaction through the interfaces among discovery services and other parties, i.e., queries and updates must be confidential with accordance to the security polices which should set the fields of the DS record to be protected.
  subtype:  bridge#process_supporting_the_privacy_of_information_in_some_RFID_related_network
     subtype:  bridge#process_supporting_anonymous_data_transactions_in_some_RFID_related_network__id_req_net_4  A party should not have to to disclose its real identity. The EPC network elements must implement access control and authentication mechanism by which anonymous data transactions can be feasible.
  subtype:  bridge#process_supporting_the_availability_of_some_RFID_related_network__id_req_net_3___NI1___NO1  EPICS systems must be resilient to Internet/local (Distributed) Denial of Service attack or failure of components, and provide back-ups facilities in order to avoid unavailability at any time.
  subtype:  bridge#process_supporting_interoperability_from/to_some_RFID_related_network__id_req_net_8___NO2  Network components should be built upon existing standards and frameworks for identity and access control.

No statement uses or specializes pm#process_supporting_the_security_of_some_RFID_related_network; click here to add one.


Simple category search: