2000
DOI: 10.5210/fm.v5i8.778
|View full text |Cite
|
Sign up to set email alerts
|

Non-repudiation in the digital environment

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
30
0

Year Published

2001
2001
2024
2024

Publication Types

Select...
3
3
3

Relationship

0
9

Authors

Journals

citations
Cited by 44 publications
(30 citation statements)
references
References 0 publications
0
30
0
Order By: Relevance
“…It states that where the law requires a signature, any method (presumably an electronic signature) is valid provided the method is reliable and appropriate for which the information is communicated. Scholars eminent in the field of electronic signatures have criticised such provisions [10,28] which make it hard for legal advisors to advise businesses to use electronic signatures. Note that post-MLEC two other set of laws, the Model Law on Electronic Signatures 2001 (MLES) and the United Nations Convention on the use of Electronic Communications in International Contracts 2005 (the Convention) have been drafted by the UNCI-TRAL that address the drawbacks in the initial model law.…”
Section: An Analysis Of Participants' Viewsmentioning
confidence: 99%
“…It states that where the law requires a signature, any method (presumably an electronic signature) is valid provided the method is reliable and appropriate for which the information is communicated. Scholars eminent in the field of electronic signatures have criticised such provisions [10,28] which make it hard for legal advisors to advise businesses to use electronic signatures. Note that post-MLEC two other set of laws, the Model Law on Electronic Signatures 2001 (MLES) and the United Nations Convention on the use of Electronic Communications in International Contracts 2005 (the Convention) have been drafted by the UNCI-TRAL that address the drawbacks in the initial model law.…”
Section: An Analysis Of Participants' Viewsmentioning
confidence: 99%
“…Security policies for SoSs rely on an communication-centric approach that maintains the integrity of system components, protects the confidentiality of information, and provides continued availability to systems [1,2]. We derive the set of policy types from industry standards including the Department of Defense Goal Security Architecture (DGSA) [3], the Common Criteria [4], Carnegie Mellon University's Computer Emergency Response Team (CERT) [2], the Federal Information Processing Standards (FIPS) minimum security requirements [5], and the NIST 800 series of publications [6]. An empirical study of these documents reveals significant corroboration of the policy types across the documents.…”
Section: Security Certification Modeling Frameworkmentioning
confidence: 99%
“…The DGSA defines seven core policy types [3]. The Common Criteria contains eleven functional classes for security policies [4]. NIST isolates security requirements across seventeen different categories [5].…”
Section: Security Certification Modeling Frameworkmentioning
confidence: 99%
“…Such systems are a cost effective way to protect the sensitive information delivered across a public data highway and to univocally identify the owner of certain credentials provided directly by the service supplier or transversely by a certification chain in a deferred way. Whereas for most electronic commerce applications such methodology fits well in a globally accepted scenario [2], in some real life situations the recourse to a deferred trusting authority results at least questionable [3]. In order to point up the spirit of such criticism we spotlight a certain dichotomy between the common sense of "trust" and the effective practice of reducing trust to a formal verification of a digital signature as in electronic commerce applications.…”
Section: Introductionmentioning
confidence: 99%