Even our definition of what is secure has evolved over the years, so code which was considered secure when it was written may turn out to be insecure after some time. There are always new ideas about security on the Internet, and an application which is secure today could be insecure tomorrow once an unknown bug (or a known behavior) is exploited in the right way. Important ways to detect and protect computers and networks against undefined behavior and security threats related to time are to keep their NTP implementations current, use an appropriate number of trustworthy time sources, and properly monitor their time infrastructure. For example, incorrect time can disrupt the ability to reconcile logfile entries on the affected system with events on other systems. If attackers can spoof the time, they may be able to bypass or neutralize other security elements. Many network security mechanisms rely on time as part of their operation. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 when, and only when, they appear in all capitals, as shown here. This document also contains information for protocol implementors who want to develop their own RFC 5905 compliant implementations. NTP operation in embedded devices is also covered. Some specific networks may have higher accuracy requirements that require additional techniques beyond what is documented here.Īmong the best practices covered are recommendatons for general network security, time protocol specific security, and NTP server and client configuration. It is intended to apply generally to a broad range of networks. The recommendations in this document are intended to help operators distribute time on their networks more accurately and more securely. This documentation is a collection of best practices from across the NTP community. NTP Version 4 (NTPv4) has been widely used since its publication as RFC 5905. NTP Implementation by the Network Time Foundation Symmetric Mode Should Only Be Used With Trusted Peers Broadcast Mode Should Only Be Used On Trusted Networks Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents () in effect on the date of publication of this document. Copyright NoticeĬopyright (c) 2018 IETF Trust and the persons identified as the document authors. This Internet-Draft will expire on May 16, 2019. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. The list of current Internet-Drafts is at. Note that other groups may also distribute working documents as Internet-Drafts. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. This documentation is a collection of Best Practices for general operation of time servers on the Internet from across the NTP community. The Network Time Protocol (NTP), currently on its fourth version, has been widely used since its initial publication. Network Time Protocol Best Current Practices Network Time Protocol Best Current Practices Internet Engineering Task Force
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |