Exam Objectives Frequently Asked Questions


Exam Objectives Frequently Asked Questions

The following Frequently Asked Questions, answered by the authors of this book, are designed to both measure your understanding of the Exam Objectives presented in this chapter, and to assist you with real-life implementation of these concepts. You will also gain access to thousands of other FAQs at ITFAQnet.com.

1.

In what format do CAs issue certificates?

microsoft certificate services use the standard x.509 specifications for issued certificates and the public key cryptography standard (pkcs) #10 for certificate requests. the pkcs #7 certificate renewal standard is also supported. windows server 2003 also supports other formats, such as pkcs #12, der-encoded binary x.509, and base64 encoded x.509, for exporting certificates to computers running non-windows operating systems.

2.

If certificates are so important in a PKI, why don’t I see more of them?

many portions of a windows pki are hidden to the end user. thanks to features such as auto-enrollment, some pki transactions can be completely handled by the operating system. most of the work in implementing a pki comes in the planning and design phase. operations such as encrypting data via efs use certificates, but the user does not see or manually handle the certificates.

3.

I’ve heard that I can’t take my laptop overseas because it uses EFS. Is this true?

maybe. the backbone of any pki-enabled application such as efs is encryption. although the u.s. government now permits the exporting of high encryption standards, some countries still do not allow their import. the windows server 2003 pki can use high encryption, and so the actual answer depends on the country in question. for information on the cryptographic import and export policies of a number of countries, see http://www.rsasecurity.com/rsalabs/faq/6-5-1.html.

4.

Can I create my own personal digital signature and use it instead of a CA?

not if you need security. the purposes behind digital signatures are privacy and security, and a digital signature at first glance seems to fit the bill. the problem, however, is not the signature itself, but the lack of trust in a recipient. impersonations become a looming security risk if you can t guarantee that the digital signatures you receive came from the people with whom they were supposed to have originated. for this reason, a certificate issued by a trusted third party provides the most secure authentication.

5.

Can I have a CA hierarchy that is five levels deep?

yes, but that s probably overkill for most networks. microsoft s three-tier model of root, intermediate, and issuing cas will more than likely meet your requirements. remember that your hierarchy can be wide instead of deep.

6.

Do I have to have more than one CA?

no. root cas have the capability to issue all types of certificates and can assume responsibility for your entire network. in a small organization, a single ca might be sufficient for your purposes. for a larger organization, however, this structure would not be suitable.

7.

How can I change the publishing interval of a CRL?

from the certification authority console, right-click the revoked certificates container and choose properties . the crl publishing parameters tab enables you to change the default interval for full and delta crls.

8.

Why can’t I seem to get auto-enrollment for user certificates to work?

remember that auto-enrollment for machines is a feature that has been around since windows 2000, but auto-enrollment for user certificates is new to windows server 2003. to use this feature, you need to be running either a windows server 2003 or windows xp client and you must log on to a windows server 2003 domain. finally, auto-enrollment must be enabled through active directory s group policy. also, you won t be able to auto-enroll a user unless the user account has been assigned an e-mail address.

9.

What is the default validity period for a new certificate?

the default, which can be changed on the general tab of a new template s property sheet, is one year. other important settings, such as minimum key size and purpose of the certificate, can be found on the sheet s other tabs.

Answers

1.

Microsoft certificate services use the standard X.509 specifications for issued certificates and the Public Key Cryptography Standard (PKCS) #10 for certificate requests. The PKCS #7 certificate renewal standard is also supported. Windows Server 2003 also supports other formats, such as PKCS #12, DER-encoded binary X.509, and Base64 Encoded X.509, for exporting certificates to computers running non-Windows operating systems.

2.

Many portions of a Windows PKI are hidden to the end user. Thanks to features such as auto-enrollment, some PKI transactions can be completely handled by the operating system. Most of the work in implementing a PKI comes in the planning and design phase. Operations such as encrypting data via EFS use certificates, but the user does not “see” or manually handle the certificates.

3.

Maybe. The backbone of any PKI-enabled application such as EFS is encryption. Although the U.S. government now permits the exporting of “high encryption” standards, some countries still do not allow their import. The Windows Server 2003 PKI can use high encryption, and so the actual answer depends on the country in question. For information on the cryptographic import and export policies of a number of countries, see http://www.rsasecurity.com/rsalabs/faq/6-5-1.html.

4.

Not if you need security. The purposes behind digital signatures are privacy and security, and a digital signature at first glance seems to fit the bill. The problem, however, is not the signature itself, but the lack of trust in a recipient. Impersonations become a looming security risk if you can’t guarantee that the digital signatures you receive came from the people with whom they were supposed to have originated. For this reason, a certificate issued by a trusted third party provides the most secure authentication.

5.

Yes, but that’s probably overkill for most networks. Microsoft’s three-tier model of root, intermediate, and issuing CAs will more than likely meet your requirements. Remember that your hierarchy can be wide instead of deep.

6.

No. Root CAs have the capability to issue all types of certificates and can assume responsibility for your entire network. In a small organization, a single CA might be sufficient for your purposes. For a larger organization, however, this structure would not be suitable.

7.

From the Certification Authority console, right-click the Revoked Certificates container and choose Properties. The CRL Publishing Parameters tab enables you to change the default interval for full and Delta CRLs.

8.

Remember that auto-enrollment for machines is a feature that has been around since Windows 2000, but auto-enrollment for user certificates is new to Windows Server 2003. To use this feature, you need to be running either a Windows Server 2003 or Windows XP client and you must log on to a Windows Server 2003 domain. Finally, auto-enrollment must be enabled through Active Directory’s group policy. Also, you won’t be able to auto-enroll a user unless the user account has been assigned an e-mail address.

9.

The default, which can be changed on the General tab of a new template’s property sheet, is one year. Other important settings, such as minimum key size and purpose of the certificate, can be found on the sheet’s other tabs.




MCSE Planning and Maintaining a Windows Server 2003 Network Infrastructure. Exam 70-293 Study Guide and DVD Training System
MCSE Planning and Maintaining a Windows Server 2003 Network Infrastructure: Exam 70-293 Study Guide and DVD Training System
ISBN: 1931836930
EAN: 2147483647
Year: 2003
Pages: 173

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net