...
Technically the transaction data is bound to entity identity data by a shared identifier (permit number) in the registration data (electronic logbook agreement), the permit database, and in e-logbook submissions. Further binding could be established by asking the e-logbook vendor to correlate customer identities to the unique keys which are embedded in each installation of certified e-logbook software. (See document binding and integrity for a broader discussion of these issues and alternatives.)
Since the Hawaii Longline Logbook is not an online application no authentication token and protocol issues are involved in non-repudiation. Technical controls for document integrity and audit trails also contribute to binding the transaction to the entity and non-repudiation, but those controls are more appropriately discussed in the next section.
...