pm#process_supporting_the_security_of_some_RFID_tag
  exclusion:  pm#process_supporting_the_security_of_some_RFID_reader  pm#process_supporting_the_security_of_some_RFID_related_network  pm#process_supporting_the_security_of_some_RFID_related_application
  supertype:  pm#process_supporting_the_security_of_some_RFID_element
  object:  bridge#RFID_tag [49..*,49..*] (pm)
  subtype:  bridge#process_supporting_authentication_in_some_RFID_tag__id_req_tag_1
     subtype:  bridge#process_permitting_an_RFID_tag_to_prove_its_identity_to_an_RFID_reader
     subtype:  bridge#process_permitting_an_RFID_tag_to_ask_its_identity_to_an_RFID_reader__TC2
     subtype:  bridge#process_preventing_an_RFID_tag_to_be_moved_to_another_product__TI3
     subtype:  bridge#process_ensuring_that_an_RFID_tag_has_only_one_EPC__TI4
     subtype:  bridge#process_verifying_an_RFID_tag_after_its_writing__TI5
     subtype:  bridge#process_authenticating_an_RFID_tag__TI6
     subtype:  bridge#process_preventing_an_RFID_tag_to_be_cloned__TI7
  subtype:  bridge#process_supporting_the_non-repudiation_of_information_sent_by_some_RFID_tag__id_req_tag_5  A reader that includes signature functionality must request that a tag signs information sent to it. With the signature, a reader can prove that a specific tag has communicated with it.
  subtype:  bridge#process_supporting_the_integrity_of_information_in/from_some_RFID_tag__id_req_tag_7  Tag must be secured against malicious writing of EPC.
     subtype:  bridge#process_securing_an_RFID_tag_against_the_malicious_writing_of_its_EPC__TI2
     subtype:  bridge#process_protecting_an_RFID_tag_when_moving_from_closed_to_open_loop__TI8
     subtype:  bridge#process_protecting_an_RFID_tag_when_moving_from_open_to_closed_loop__TC4
  subtype:  bridge#process_supporting_the_confidentiality_of_communication_between_RFID_tag_and_reader__id_req_tag_2  Communication between tag and reader must be encrypted for applications that need to prevent eavesdropping of the contact-less channel.
  subtype:  bridge#process_supporting_the_privacy_of_information_in_some_RFID_tag__id_req_tag_4
     subtype:  bridge#process_permitting_to_disable_an_RFID_tag_when_it_is_not_within_company-influence__TC1
        subtype:  bridge#process_permitting_to_disable_an_RFID_tag_when_it_is_sold_to_a_final_user__TC3
  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_interoperability_from/to_some_RFID_tag__id_req_tag_8  The tag must comply with EPC, maybe with temporary IDs, or restrict access to some protected memory only to authenticated readers. This allows to apply secure tags in standard supply chains but makes secure operation possible (e.g. after POS).
     subtype:  bridge#process_permitting_a_secure_RFID_tag_to_operate_with_existing_insecure_readers__TO1

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