Rule 13, Digital Signature (End Entity) Rules, 2015: 3T#T ^ T R R f ^ T TTR^rT
Digital Signature (End Entity) Rules, 2015 - Rule 13
Text of rule 13
3T#T ^ T R R f ^ T TTR^rT
13. 3T#T ^ T R R f ^ T TTR^rT.— ̂ FcTTSTC ter a fa ^ ^ ^ T f ^ # ^TT^ 3 f€ fa ^ ^ ^ ^ ^ ^ H c ^ m
(i) snfto i^rrsn; M^mm % f%̂ I^^TT vflsftftfl srf&f^nr % srefk ̂ ir€r srtoforft irpfcsfa
(ii) *rrerft%3n^% f^rr rr^r.509 ym«i4i 3rRr;
(iv) Mmun-uui STRJ+IR^ (€trr) % f̂ tT asrf?r?rr̂ r f̂mrT r̂ srrf&rRr vfid\+M (sMrt^rft) % r̂
(v) w , «mTr1^rTT l^ (^ )%f%^ ; f l ^ *^
[W.tf. 19/26/2015-^ftq;]
MINISTRY OF COMMUNICATIONS AND INFORMATION TECHNOLOGY
(Department of Electronics and Information Technology)
NOTIFICATION
New Delhi, the 25th August, 2015
G.S.R. 660(E).—In exercise of the powers conferred by section 87 of the Information Technology Act, 2000
(21 of 2000), the Central Government hereby makes the following rules, namely:—
I. Short title and commencement.—
(1) These rules may be called the Digital Signature (End entity) Rules, 2015.
(2) They shall come into force on the date of their publication in the Official Gazette.
Definitions—(l)In these rules, unless the context otherwise requires,—
^a) A n " u i w i u tho Information TAf-hnnlngy A c t 2000(2t o f 2000);
(b) "canonicalisation", in relation to a xml digital signature, means the process of converting electronic record that
has more than one possible representation into a 'standard', 'normal', or 'canonical form' in which the variations
12 THE GAZETTE OF INDIA: EXTRAORDINARY [PART 11--SKC 3(1)].
in representation of electronic record shall be standardised by applying consistent rules, primarily as part of the
xml digital signature creation and verification processes;
(c) "counter signature" means a signature on a previous signature in a series of signatures, affixed after the
verification the signature on electronic record and subsequent signatures on previous signatures serially;
(d) "detached signature" means the signature that is stored independent of electronic record being signed;
(e) "digestniethod element", in relation to a xml digital signature, means the digest algorithm to be used for the-
original data object or transformed, if any 'xml transforms' exists;
(f) "digestvalue element" means the value of the digest;
(g) "end entity" means the subscriber or system on behalf of the subscriber in whose name the Electronic Signature
Certificate is Issued;
(h) "end entity signature" means authentication of any electronic record by an end entity by means of a digital
signature, electronic method or procedure in accordance with the provisions of sections I » I A t>e*h* Aotj .
(1) "enveloped signature" means enveloping of the signature and the initial electronic record into another
electronic record;
S (j) "enveloping signature" means a signature over a electronic record that is referenced and contained within the
signature element;
(k) "initial electronic record", in the context of xml digital signature process* means canonicaiised and transformed
formofsigncdlnfo;
(1) "keyinfo element" means an element that enables key information to be packaged along with the signature
element;
(m) "long term signature" means a signature element that is made verifiable for a long term by implementing
measures to enable the detection of unauthorised alterations of signature;
(n) "manifest element", In relation to a xml digital sipature, means a structure to carry a list of reference elements
processing model defined by the application;
(o) "object element" means an optional element of xml digital signature, which is used for enveiopina signature
whsfA th* data object being signed Is included in (.lie xrill;
(p) "ocsp responded means an online service that provides revocation status of a digital signature certificate;
(q) "online certificate status protocol" means an online certificate-revocation checking protocol that enables relying-
parties to determine the revocation status of an Identified digital signature certificate;
(r) "parallel signatures" means one or more independent signature over the same electronic record in which the
ordering of the signatures is not important;
(s) "reference element", in relation to a xml digital signature, means an element that carries a references to data
objects, an optional list of transforms to be applied prior to digest (xml transforms), digestmethod and
digestvalue value of referenced data objects;
(t) "slgnedinfo", in relation to a xml digital signature, means an element that contains a set of information to be
signed for creating an xml signature, where it shall contains references to the data object that Includes the
canonicalisation and signature algorithms;
(u) "signature" means digital signature or xml digital signature;
(v) "signature value" means an airman* that tke actual value of the digital signature,
(w) "signaturemethod " means an element that contains the algorithm used for signature generation and this
algorithm identifies all cryptographic functions involved In the signature generation;
[qm it-grog 3(j)J iqRff ^T TOTS ; WBWrW 13
(x) "signatureproperties" means an element that provides a way to carry additional information about the signature,
such as a time stamp or any other information which are defined by application;
(y) "time stamp" means a notation that indicates the correct date and time of an action and Identity of the person or
device that sent or received the time stamp and is enforced using time stamp token;
(z) "time stamp token " moans a cryptographically secure confirmation generated by applying digital signature of a
time stamping service provider that Includes the time when the confirmation was generated;
(za) "time stamping service provider" means a trusted entity authorised to generate time stamps;
(2b) "xml" means Extensible Markup Language that provides a standard methodology with formal syntax to identify
elements of information, describe the structure of data and also to store data in an Independent manner, shall
have the following properties,—
(i) with xml, content and presentation are separate;
(ii) the structure of xml data in a particular context is described using either xm! schema or a document
type definition;
(Hi) xml schema or a document type definition are stored separately from die xml document itself and can
be us«d to iraliduU. a g ir tn mill dwvuiiiEiu AJI bUiifUi jimiiuc,
(zc) "xml digital signature element" means an element that defined by standard xml schema for capturing the result of
a digital signature operation applied to arbitrary data, in xml format, shall satisfy the following,—
(i) xml digital signature element shall exist as a standalone document or envelop the data object that it signs;
(II) xm! digital signature element shall have signedinfo, signature value, keyinfo, object and has id attribute
of type child elements in order in which they appear;
(zd) "xml digital signature" means the digital signature on xml electronic record;
(ze) "xml document" means a document with xml logical and physical structure that Is used to carry data elements,
composed of declarations, elements, comments, character references, and processing instructions and a physical
structure composed of entitles, starting with the root, or document entity;
(zf) "xml schema" means a set of pre-defined or user defined keywords and their attributes arranged In a structured
manner, shall satisfy the following,—
(i) should be used for a particular purpose where as a schema describes the structure of an xml document and
provides specification of element names that indicates which elements are allowed in an xml document,
and in what combinations; and
(il) should provide extended functionality such as data types, inheritance, and presentation rules and default
values for attributes;
<zg; "xmi transform" means an element mat specify an optional ordered list of processing steps applied to the data
objects before it was digested where the transforms Include canonicalization, encoding or decoding, extensible
style sheet language transformations, xpath filtering, and xml schema validation;
(zh) "xml namespace" means a uniform resource Identifier (uri) reference where the mechanisms described in the
specification are used in xml documents as element types and attribute names and also to use various xml
vocabularies without having name collision.
(2) Words and expressions used herein and not defined but defined in the Act shall have the meanings respectively
assigned to them in the said Act,
3. Manner of authentication of Information by means of digital signature,—A digital signature shall,—
(a) be created and verified by cryptography which concerns with transforming electronic record into seemingly
unintelligible forms;
(b) use Public Key Cryptography, which employs an algorithm using two different but mathematical related
keys; one key (called tho private key) for creating a digital signature and another key (called the public key)
for verifying a digital signature;
(c) use an hash function for creating and verifying a digital signature which required to make digital signature
generation and verification efficient.
4. Creation of digital signature—(1) The signatory shall, while signing an electronic record or any other item of
information, first apply an hash function in the signatory's hardware or anfVwnm
14 THE GAZETTE OF INDIA ; EXTRAORDINARY [PARTU—SEC. 3fiJ]
(2) The hash function shall produce a hash result.
(3) The signatory's hardware or software shall then transform the hash result into a digital signature using signatory's
private key and signature algorithm.
(4) The contextual information like date and time, shall be then made part of the digital signature.
(5) The counter signatures or parallel signatures or both may also be applied to electronic record.
(6) The following information may also be a part of signature,-—
(a) the signatory's public key signature certificate(s);
(b) the public key certificate(s) of the licensed Certifying Authorities which used to verify the authenticity of
the digital signature certificate issued to the signatory;
(c) the self signed certificate generated by the Controller used to verify the authenticity of the public key
certificate of the licensed Certifying Authorities;
(d) the certificate revocation list(s) maintained by the licensed Certifying Authorities, and the controller which
is used to check whether the digital signature certificate has been revoked under section 38 the Act;
(e) online certificate status protocol responder certificates and online certificate status protocol responses that
may be used in lieu ot certificate revocation iisu
(7) To create long term valid digital signature,—
(a) a timestamp shall be applied initially to the signed data including the certificates and revocation
information;
(b) ensure that initial time stamp shall cover all the data and signature(s);
(c) a nested time stamp option shall be used to ensure signature validity past the time stamping service
provider's (tssp) key or algorithm expiry where the nesting of time stamps implies that a subsequent time
stamp shall be applied to the prior time stamp;
(d) signature(s) and time stamps may be embedded in the data itself or stored separately as standalone.
5. Verification of digital signature.—(l)The verification of a digital signature shall be accomplished by computing a
new hash result of the original electronic record by means of the hash function used to create a digital signature and by
using the public key and the new hash result, the verifier shall check—
(a) if the digital signature was created using the corresponding private key and shall be applicable for parallel and
counter signatures applied on the electronic record, if present;
(b) the time when the digital signature was created.
(2) To verify counter signature, the signature on electronic record and thereafter signature on previous signature serially
i ljall b e vbi i f ibd.
(3) To verify parallel signature, signature on electronic record shall be verified independently.
(4) To verify long term signature, the initial timestamp and all subsequent time stamp applied on the each prior
timestamp shall be verified.
6. Verification of Digital Signature Certificate.—(1) The self signed certificate generated by the Controller, which
begins the trust chain for the public key infrastructure, shall be used to verify the authenticity of the public key
certificate of the licensed Certifying Authorities.
(2) The public key certificate of the licensed Certifying Authorities shall be used to verify the authenticity of the
digital signature certificate issued to the subscribers.
(3) The certificate revocation list maintained by the licensed Certifying Authorities shall be checked to confirm
whether the certificate of the licensed Certifying Authorities is valid or whether it has been revoked under
section 38 the Act.
(4) While verifying the validity of a digital signature the corresponding digital signature certificate shall chain up
through the public key certificate of the issuing Certifying Authority to the self signed certificate of the
Controller and if any of the certificates in the trust chain is not trusted the signature shall not be verified.
(5) The Digital Signature Certificate shall be verified with respect to time of signature created.
(6) The chain of certificates shall be verified in accordance with the standards specified in rule 7.
(7) If the certificate validity is less than one hour, the checking of revocation list shall not be required.
i
[*TR Il-ig^rg 3(j)] **Ku" ^1 TFF& : sraî TTFT 15,
7. Digital signature standards.—The most important standards that shall be applicable for different activities
associated with digital signature functions are as under—
Products
Cryptographic hash function
RSA Public Key Technology
Encryption and digital signature
Validation of Digital Signature Certificate
ECC curve
Long term signature formats
Time stamp token
Standards
SHA-2 as specified in F1PS 180-4
PKCS#1 RSA Encryption Standard ([2048,4096
bit)); Version 1.5
PKCS#7, CMS
RFC 5280
NISTP-256,P-384,orP-521
l.CAdES RFC 5126,
2. PAdES with CAdES
As specified R!U3]t>i
8. Manner of authentication of information by means of xml digital signature.— A xml digital signature shall,—
(a) be created and verified by cryptography which concerns with transforming electronic record into seemingly
unintelligible forms;
(b) use Public K.ey Cryptography, which employs an algorithm using two different but mathematical related keys,
one key (called the private key) for creating a xml digital signature and another key (called the public key) for
verifying a xml digital signature;
(c) use an cryptographic hash function for creating and verifying a xml digital signature;
(d) use canonicalization and xml transformation to create standard electronic record prior to creation and verification
of xml digital signature;
(e) authenticate xml documents which contain data as references and corresponding hashes, which is affected by the
use of hash algorithm, canonicalization, xml transformation and public key algorithm.
9. Creation of xml digital signature.—(1) To sign an electronic record or any other item of information, the signatory
shall first constructs reference elements, xml digital signature element, signedinfo, keyinfo and signaturevalue.
(2) For the purpose of reference element generation, the signing software shall—
^J creaie reierente^s) cituisin.(a) rritu i-afonsince to tk» itam of in-form at inn, vml transform elementfsl (optional),
digest algorithms and digest value;
(b) optionally apply xml transform(s) to each referenced object in a sequential order;
(c) apply the hash function in the signatory's hardware or software to each reference elements, store the hash result
m the reference element;
(d) ensure that if the object element is created, it shall not have a manifest element;
(e) ensure that exclusive canonicalization "without comments" has been mandatorily specified in addition to any
other transforms.
(3) For the purpose xml digital signature generation, the signing software shall—
(a) create signedinfo element with signaturemethod, canonicalisation method and reference^);
(b) apply canonicalisation to signedinfo and calculate the hash value of canonicalised signedinfo using the hashing
algorithms implied by the signaturemethod;
(c) ensure that,—
(i) the signatory has seen all the contents of the document before signing;
(ii) the contents display requirements, in the case of automated signing process, is not required;
{\l\) 10 Sign IIlUlUpIC I t i u u i ™ t v 6 * t b « ,
(a) each resource shall be rendered on the screen;
16 T! IE OAgKTTE OF INDIA : EXTRAORDINARY [PART II—SEC, 3(i)J
(b) each referenced xml resource shell he rendered using xsit and the xslt shall he the last transform
done to render the resource on the screen;
(c) each non xml resource shall he rendered using mimetype Attribute mentioned In the object;
(d) generate the signature using the signature algorithm and the hash, the signatory's private key, and
the public key parameters (if applicable) and perform bnse64 encoding of the signature result and
use It to form signal urevalue;
(e) construct the signature element that Includes signedlnfo, Items of Information, keylnfo with *509
certificate element and signaturevalue and the x509 certificate element shall carry the signatory's
x5Q9 public key certificate,
(4) The contextual information like date and time, shall be then made part of the xmi digital signature.
(5) The counter signatures or parallel signatures or both may also be applied to electronic record,
•
(6) The following Information may also be a part ol'slgnature—
(a) the public key certlflcate(s) of the licensed Certifying Authorities which used to verify the authenticity of
the digital signature certificate Issued to the signatory;
(bj Uw atir Milieu certificate generated by the Controller used to verify the authenticity of the public key
certificate of the licensed Certifying Authorities;
(c) the certificate revocation llst(s) maintained by the licensed Certifying Authorities and controller which Is
used cheek whether the digital signature certificate has been revoked under section 38 the Act;
(d) online certificate status protocol responder certificates and online certificate status protocol responses may
be used in lieu of certificate revocation list,
(7) To create long term valid xml digital signature—
(a) a timestamp shall be applied Initially to the signed document, where the Initial time stamp shall cover all
the electronic record and slgnature(s);
(b) a nested time stamp option shall be used to ensure signature validity past the time-stamping service
provider (tsspj's key or algorithm expiry where as nesting of time stamps implies that a subsequent time
stamp shall be applied to the prior time stamp;
(c) signature(s) and time stamps may be embedded In the data Itself or stored separately as standalone.
(0. Verification of xml digital signature. - ( I ) The verification of the xml digital signature shall be accomplished by
signature validation, reference validation and certificate validation and an xml digital signature shall be treated valid
only I ('signature validation, reference validation and certificate validation as specified below are complied with.
(2) To accomplish signature validation—
(a) canonical form of signedlnfo as produced during reference validation shall be used;
(b) canonical form of signaturemethod using the canonical lotion method shall be obtained;
(c) the public key contained in the signatory's x509 certificate that Is included In the xmi digital signature, the
canonlcalisied form of signedlnfo signaturevalue, and canonlcaltsled form of signaturemethod shall be used
to verify the signature,
(3) To accomplish reference validation^
(a) canonlcaiise the signedlnfo element based on the canon icalisation method In the signedlnfo shall be used;
(b) for each reference in the signedlnfo—
(I) if transformations were applied by the signatory, then the verifier software may de-reference the
uniform resource identifier (url) and execute transforms provided by the signatory In the reference
element;
(II) compute digest of referenced item using the digestmethod specified In Its reference element;
(iil) compare the computed digest value against dlgestvalue in the signedlnfo reference; If there la any
mismatch or validation fails;
(4) The Digital Signature Certificate Included in the xml digital signature shall be verified in accordance with the
fwnvMoiifl gpvctflad In rule 6,
(5) To verify counter signature, the signature on electronic record first and signature on previous signature shall be
verified serially,
[*jgj l i - ^ r g 3(i)] ^Rcf ^T *|sPT:f : srarqKT 17
(6) 1 o verify parallel signature, signature on electronic record shall be verified independently.
(7) To verify long term signature, the initial timestamp and all subsequent time stamp applied on the each prior
timestamp shall be verified.
11. The xml digital signature standards.—The most important standards that shall be applicable for different activities
associated with xrol digital signature functions are as under—
The Product
XML Digital Signature Standard
XML "Namespace •
Signature encoding
Signature Value Encoding
Reference element Digest
Signature Algorithm
Signature block Canonicalization
Transform Algorithms
Signature Type
Digital Signature Certificate
Standard
RFC 3275 with the following constraint
o Manifest is not permitted inside Object,
o Keylnfo containing X509Certificate element is mandatory.
o The Reference Processing shall use the Exclusive
Canonicalization(without comments) in addition to other transforms.
o For XML resource. XSLT shall be the last transform done to enable the
rendering of the documeni on screen.
o For rendering of document on the screen
o Each referenced XML resource shall be implemented using XSLT.
o Each non XML resource shall be implemented using Mime Type
attribute mentioned in the object.
RFC 3986
UTF-8 RFC 3629
Rasc64 RFC 4648
SHA256 MPS 180-4
SHA256withRSA FKCS-1 Version 1.5
a Exclusive (without comments), XML-EXC-CI4N, RFC 3741
Canonical XML
1. Canonical XML 1.0 (omits comments)
littpi/AvwwwS.ore'TR/lOOiyREC nml ol-tn 20010315
2. Canonical XML 1,1 (omits comments)
http://www.w3.org/2006/12/xml-cl4nll
Exclusive (without comments), XML-EXC-C14N, RFC 3741
Canonical XML-
1. Canonical XML LO (omits comments)
http://www.w3 .org/TR/2001/REC-xml- cl to-20010? 15
2, Canonical XML 1.1 (omits comments)
http://www.w3.org/2006/! 2/xml-c 14n 11
XSLT-XSL Transforms (XSLT) Version 1.0. W3C
http://www.w3.org/TR/1999/REC-xslt-19991116
XPath-RFC 3653
enveloped or enveloping or detached
(DER) X-309 Vi issued as per interoperability guidelines
1
^ ' H ^ H - ^
http://www.w3.org/2006/12/xml-cl4nll
http://www.w3
http://www.w3.org/2006/
http://www.w3.org/TR/1999/REC-xslt-19991
_US THE GAZETTE OF ]NDIA : EXTRAORDINARY [PART H—SEC. 3 (j)]
Public Key Algorithms
ECC curve
Long Term Signature formats
Time Stamp Token
RSAPKCS-1 Version 1.5
NISTP-256,P-384JorP-52]
LXMLERS RFC 6283 and XAdES
2. XMLERS RFC 6283 and PAdES with XAdES
As specified RFC 3161 in XML notation
12. The basic Syntax of xml digital signature and terms used in the rule shall be as follows, namely:-
<Signature ID?>
<Signedlnfo>
<Canon icalizationMethod/>
<S ignatureMetllod/>
(<Reference URI?>
(<Transforms>)?
<DtgestMethod>
<DigestValue>
</Reference>+
</SignedInfo>
<SignatureValue>
(<KeyInfo>
(KeyName)
(KeyValue)
(RetrievalMethod)
(<X509Data>
(X509SK1)
(X509SubjectName)
(X509Certificate)
(X509CRL)
(X509Digest)
</x509Data>)
</keyihfo>)
(<Object ID?>)*
</Signature>
I _.. ... _ _ _ ™ _ „ _ _ ^ _ _
Wliere "?" denotes zero or one occurrence; "+" denotes one or more occurrences; and "*" denotes zero or more
occurrences"
[qFT l\-W*Z 3(i)] . ^R3 *ET WTO : 3P3!*mTT 1£
13. Digital Signature functions Standard.— The manner of digital signature creation and verification, in respect of
signature profile and signature format, shall also conform to the following guidelines issued by Controller, namely:-
(i) Interoperability Guidelines for Digital Signature Certificates issued under Information Technology Act;
(ii) X.509 Certificate Policy for India PK.I;
(iii) Signature profiles;
(iv) Online Certificate Status Protocol (OCSP) Service Guidelines for Certifying Authorities (CA);
(v) Time Stamping Services Guidelines for Certifying Authorities (CA).
[F.No. 19/26/2015-CCA]
TAPAN RAY, Addl. Secy.
Tt f t^ f t , 25 3TW, 2015
wr.w.fa. 661(3T).— ̂ f a flTSfnr, SĴ PTT ifYifiM srrlrf̂ rfT, 2000 (2000 w 21) #r srrcr 16 %
*rnr Tf^r SIFT 87 ̂ t STOKT (2) ̂ nts1 (T) srcr STSTT ?ir*it ?r ^rnr ^AT^T ^^TT t̂sriPi<fi (*J<.ISII urstmi)
f^PT, 2004 W afhC t?fr*FT *&$ % f^r f^rfM%?T f^WWmtfr|, 3RT^ :--
1 .(1) ^r f^mt ^r ?if$rHr ?mr g w ifl̂ HPifl ( ^ r r TjfitaryttfnFT f^pr, 201511
2. ^ r r ifl̂ nRifl (^:§TT ̂ r r ) f̂ r*r, 2004 *f,-
(?) %PT2f, ^(^)%FrrffqTplHpif^d w^WT^Trnrr, apsrr^:-
(arRrir ftunr) R w , 2015 # qfbnf^a | , ?r JPW: w r̂ a*«f strr wt S^FT 3 W arf^f^rsr aftr
f ^ w t ^ t i " ;
(«r) pfcpT41, ̂ w (^)%wr'RRnRlRlct «i« <ii wnpn, arefq;:-
"(**) 3i#*r ^rrsrr (att%T R*w) f^w, 2015 V Pfew 7 m f ^ r 12 *f RRtd JTT F̂T w, ^ r ^r?
^T^T #^r atfr̂ r ^ r r e r r % ^ R , *TST<UI Mk 4I\NUI %|, ^ H M H cp̂ f ^ ?prr | ; #c
t*rr. TT. 1O/26/2015 rfhfrrrj
<PR Tpr, srqr *rf%̂
fc*nT : ĝ r PTTT wr^r % <.MH*I, 3mTmmr, w r H, ^ 3, s w (i) ^ arRrg^Rr *f. wT.̂ rf̂ . 735(3T).
' lTfr^29 3TW^r2014^Kr^fr%crr%^7TTr ^ |
NOTIFICATION
New Delhi, the 25th August, 2015
G.S.R. 661(E).—In exercise of the powers conferred by clause (e) of sub-section (2) of Section 87 read with
Section 16 of the Information Technology Act, 2000 (21 of 2000), the Central Government hereby makes the following
rules to amend me Information Technology (Security Procedure) Rules, 2004.
1.(1) These rules may be called the Information Technology (Security Procedure) Amendment Rules, 2015.
(2) They shall come into force on the date of their publication in the Official Gazette.
2. In the Information Technology (Security Procedure) Rules, 2004,—
(a) in rule 2, for clause (e)> the following clause shall be substituted, namely:—
"(e) words and expressions used in these rules and not defined but defined in the Act and the Digital Signature (bna
entity) Rules, 2015 shall have the same meaning respectively assigned for them in the said Act and rules,";
Previous and next
All provisions of Digital Signature (End Entity) Rules, 2015
Questions people ask
Is rule 13 of Digital Signature (End Entity) Rules, 2015 still in force?
No repeal of Digital Signature (End Entity) Rules, 2015 is recorded.