pm#process_supporting_the_availability_of_some_RFID_related_entity_or_process
  exclusion:  pm#process_supporting_authentication_in_some_RFID_related_entity_or_process  pm#process_supporting_the_non-repudiation_of_information_sent_or_received_by_some_RFID_related_entity_or_process  pm#process_supporting_the_access_control_of_some_RFID_related_entity_or_process  pm#process_supporting_the_integrity_of_information_in/from_some_RFID_related_entity_or_process  pm#process_supporting_the_confidentiality_of_communication_with_some_RFID_related_entity_or_process  pm#process_supporting_the_privacy_of_information_in_some_RFID_related_entity_or_process  pm#process_supporting_interoperability_from/to_some_RFID_related_entity_or_process
  supertype:  pm#process_supporting_some_security_attribute_in_some_RFID_related_entity_or_process
  subtype:  bridge#process_supporting_the_availability_of_access_to_information_in_some_RFID_tag__id_req_tag_3___TI1  Tags should not be disabled when product is being used by business process.
  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_the_availability_of_some_RFID_related_application__id_req_app_3  DS must be able to provide mechanism whereby prevent users from monopolising the resources.

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