DOCSLIB.ORG

TCP+UDP Ports

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
TCP+UDP Ports TCP+UDP Ports Port Transport Description Port Transport Description Shirt Pocket netTunes; Shirt Pocket 47 TCP, UDP NI FTP 0 TCP launchTunes 48 TCP, UDP Digital Audit Daemon 1 TCP TCP Port Service Multiplexer (TCPMUX) 49 TCP, UDP TACACS+; TACACS 2 TCP, UDP Management Utility 50 UDP Remote Mail Checking Protocol (RMCP) 3 TCP, UDP Compression Process 51 TCP, UDP Logical Address Maintenance (IMP) Self-Certifying File System (SFS); Midnight 52 TCP, UDP XNS Time Protocol 4 Commander 53 TCP, UDP Domain Name System (DNS) 5 TCP, UDP Remote Job Entry 54 TCP, UDP XNS Clearinghouse 6 55 TCP, UDP ISI Graphics Language 7 TCP, UDP Echo 56 TCP, UDP XNS Authentication 8 57 TCP Mail Transfer Protocol (MTP) 9 SCTP, TCP, UDP Discard 58 TCP, UDP XNS Mail 10 59 TCP NFILE 11 TCP, UDP SYSTAT 60 12 61 TCP, UDP NI MAIL 13 TCP, UDP Daytime 62 TCP, UDP ACA Services 14 63 TCP, UDP Whois++ 15 Netstat 64 TCP, UDP CI, Communications Integrator 16 65 TCP, UDP TACACS-Database Service 17 TCP, UDP Quote of the Day 66 TCP, UDP Oracle SQL*NET Remote Write Protocol (RWP); Message 67 UDP Bootstrap Protocol server (BOOTP) 18 TCP, UDP Send Protocol 68 UDP Bootstrap Protocol client (BOOTP) 19 TCP, UDP Character Generator Protocol (Chargen) 69 UDP Trivial File Transfer Protocol (TFTP) 20 TCP File Transfer Protocol (FTP) 70 TCP Gopher 21 TCP File Transfer Protocol (FTP) 71 TCP, UDP Remote Job Service 22 SCTP, TCP Secure Shell (SSH) 72 TCP, UDP Remote Job Service 23 TCP Telnet 73 TCP, UDP Remote Job Service 24 Any private mail system 74 TCP, UDP Remote Job Service 25 TCP Simple Mail Transfer Protocol (SMTP) 75 Any private dial out service 26 76 TCP, UDP Distributed External Object Store 27 TCP, UDP NSW User System FE 77 Any private RJE service 28 78 TCP, UDP vettcp 29 TCP, UDP MSG ICP 79 TCP Finger 30 80 TCP HyperText Transfer Protocol (HTTP) 31 TCP, UDP MSG Authentication 81 32 82 TCP, UDP XFER Utility 33 TCP, UDP Display Support Protocol 83 TCP, UDP MIT ML Device 34 84 TCP, UDP Common Trace Facility 35 Any private printer server 85 TCP, UDP MIT ML Device 36 86 TCP, UDP Micro Focus Cobol 37 TCP, UDP Time Protocol 87 Any private terminal link 38 TCP, UDP Internet Route Access Protocol (RAP) 88 UDP Kerberos 39 UDP Resource Location Protocol (RLP) 89 TCP, UDP SU/MIT Telnet Gateway 40 Used unofficially by Pointcast; DNSIX 41 TCP, UDP Graphics 90 TCP, UDP Securit Attribute Token Map 42 UDP Internet Name Server 91 TCP, UDP MIT Dover Spooler 43 TCP Whois 92 TCP, UDP Network Printing Protocol 44 TCP, UDP MPM FLAGS Protocol 93 TCP, UDP Device Control Protocol 45 TCP Internet Message Protocol 94 TCP, UDP Tivoli Object Dispatcher 46 TCP, UDP MPM Created by Devyn Collier Johnson <[email protected]> (2015 v2) More cheatsheets at DCJTech.info TCP+UDP Ports Port Transport Description Port Transport Description 95 SUPDUP 144 Universal Management Architecture 96 TCP, UDP DIXIE 145 UAAC Protocol 97 TCP, UDP Swift Remote Virtual File Protocol 146 98 TCP, UDP TAC News 147 UDP ISO-IP 99 TCP, UDP Metagram Relay 148 Jargon 100 149 AED 512 Emulation Service 101 TCP HOSTNAME 150 SQL-NET 102 TCP TP0 over TCP 151 HEMS 103 TCP, UDP Genesis Point-to-Point Trans Net 152 TCP Background File Transfer Program (BFTP) 104 Simple Gateway Monitoring Protocol 105 TCP Ph; Mailbox Name Nameserver 153 UDP (SGMP) 106 3COM-TSMUX 154 NETSC 107 Remote Telnet Service 155 NETSC 108 SNA Gateway Access Server 156 SQL Service 109 TCP Post Office Protocol v2 (POP2) 157 KNET/VM Command/Message Protocol 110 TCP Post Office Protocol v3 (POP3) 158 TCP Distributed Mail Service Protocol (DMSP) 111 Portmapper 159 NSS-Routing 112 McIDAS Data Transmission Protocol 160 SGMP-TRAPS 113 TCP Identification Protocol Simple Network Management Protocol 161 TCP, UDP (SNMP) 114 Simple Network Management Protocol 115 TCP Simple File Transfer Protocol (SFTP) 162 TCP, UDP traps (SNMP) 116 ANSA REX Notify 163 CMIP/TCP Manager 117 TCP Unix To Unix Copy (UUCP) 164 CMIP/TCP Agent 118 SQL Services 165 Xerox 119 TCP Network News Transfer Protocol (NNTP) 166 Sirius Systems 120 UDP Coherent File Distribution Protocol (CFDP) 167 NAMP 121 168 RSVD 122 SMAKYNET 169 SEND 123 UDP Network Time Protocol (NTP) 170 Network PostScript 124 ANSA REX Trader 171 Network Innovations Multiplex 125 Locus PC-Interface Net Map Serv 172 Network Innovations CL/1 126 Unisys Unitary Login 173 Xyplex 127 Locus PC-Interface Conn Server 174 MAILQ 128 GSS X License Verification 175 VMNET 129 TCP, UDP Password Generator Protocol (PWDGEN) 176 GENRAD-MUX 130 cisco FNATIVE X Display Manager Control Protocol 131 cisco TNATIVE 177 (XDMCP) 132 cisco SYSMAINT 178 NextStep Window Server 133 TCP, UDP Statistics Server (STATSRV) 179 TCP BGP, Border Gateway Protocol 134 INGRES-NET Service 180 TCP, UDP Intergraph 135 DCE endpoint resolution 181 TCP, UDP Unify 136 PROFILE Naming System 182 TCP, UDP Unisys Audit SITP 137 NETBIOS Name Service 183 OCBinder 138 NETBIOS Datagram Service 184 OCServer 139 NETBIOS Session Service 185 Knowbot Information Service 140 EMFIS Data Service 186 KIS Protocol 141 EMFIS Control Service 187 Application Communication Interface 142 Britton-Lee IDM 188 Plus Five's MUMPS 143 TCP Interactive Mail Access Protocol (IMAP) 189 Queued File Transport Created by Devyn Collier Johnson <[email protected]> (2015 v2) More cheatsheets at DCJTech.info TCP+UDP Ports Port Transport Description Port Transport Description 190 Gateway Access Control Protocol 238 191 Prospero Directory Service 239 192 OSU Network Monitoring System 240 193 Spider Remote Monitoring Protocol 241 194 Internet Relay Chat Protocol 242 Direct 195 DNSIX Network Level Module Audit 243 Survey Measurement 196 DNSIX Session Mgt Module Audit Redir 244 Dayna 197 Directory Location Service 245 LINK 198 Directory Location Service Monitor 246 Display Systems Protocol 199 TCP SMUX 247 SUBNTBCST_TFTP 200 IBM System Resource Controller 248 bhfhs 201 AppleTalk Routing Maintenance 249 202 AppleTalk Name Binding 250 203 AppleTalk Unused 251 204 AppleTalk Echo 252 205 AppleTalk Unused 253 206 AppleTalk Zone Information 254 207 AppleTalk Unused 255 208 AppleTalk Unused 256 RAP 209 The Quick Mail Transfer Protocol 257 Secure Electronic Transaction 210 258 Yak Winsock Personal Chat 211 Texas Instruments 914C/G Terminal 259 UDP Efficient Short Remote Operations (ESRO) 212 ATEXSSTR 260 Openport 213 IPX 261 IIOP Name Service over TLS/SSL 214 VM PWSCS 262 Arcisdms 215 Insignia Solutions 263 HDAP 216 Border Gateway Multicast Protocol 217 dBASE Unix 264 TCP (BGMP) 218 TCP Message Posting Protocol (MPP) 265 X-Bone CTL 219 Unisys ARPs 266 SCSI on ST IMAP, Interactive Mail Access Protocol, 267 Tobit David Service Layer 220 TCP version 3 268 Tobit David Replica 221 Berkeley rlogind with SPX auth 269 MANET protocols 222 Berkeley rshd with SPX auth 270 UDP GIST Q-mode messages 223 Certificate Distribution Center IETF Network Endpoint Assessment (NEA) 224 Posture Transport Protocol over TLS (PT- 271 TCP TLS) 225 272 226 273 227 274 228 275 229 276 230 277 231 278 232 279 233 280 http-mgmt 234 281 Personal Link 235 282 Cable Port A/X 236 283 rescap 237 284 corerjd Created by Devyn Collier Johnson <[email protected]> (2015 v2) More cheatsheets at DCJTech.info TCP+UDP Ports Port Transport Description Port Transport Description 285 333 Texar Security Port 286 FXP-1 334 287 K-BLOCK 335 288 336 289 337 290 338 291 339 292 340 293 341 294 342 295 343 296 344 Prospero Data Access Protocol 297 345 Performance Analysis Workbench 298 346 Zebra server 299 347 Fatmen Server 300 348 Cabletron Management Protocol 301 349 mftp 302 Mapping of Airline Traffic over Internet 303 350 TCP Protocol, Type A (MATIP) 304 Mapping of Airline Traffic over Internet 351 TCP Protocol, Type B (MATIP); bhoetty 305 352 DTAG 306 353 NDSAUTH 307 354 bh611 308 Novastor Backup 355 DATEX-ASN 309 EntrustTime 356 Cloanto Net 1 310 bhmds 357 bhevent 311 AppleShare IP WebAdmin 358 Shrinkwrap 312 VSLMP 359 Tenebris Network Trace Service 313 Magenta Logic 360 scoi2odialog 314 Opalis Robot 361 Semantix 315 DPSI 362 SRS Send 316 decAuth 363 UDP RSVP Tunnel 317 Zannet 364 Aurora CMGR 318 TCP Time Stamp Protocol (TSP) 365 DTK 319 PTP Event Simple Mail Transfer Protocol (SMTP); On- 320 PTP General 366 TCP Demand Mail Relay (ODMR) 321 PIP 367 MortgageWare 322 RTSPS 368 QbikGDP Internet Message Mapping Protocol 369 rpc2portmap 323 (IMMP) 370 codaauth2 324 371 Clearcase 325 372 ListProcessor 326 373 Legent Corporation 327 374 Legent Corporation 328 375 Hassle 329 376 Amiga Envoy Network Inquiry Proto 330 377 NEC Corporation 331 378 NEC Corporation 332 379 TIA/EIA/IS-99 modem client Created by Devyn Collier Johnson <[email protected]> (2015 v2) More cheatsheets at DCJTech.info TCP+UDP Ports Port Transport Description Port Transport Description 380 TIA/EIA/IS-99 modem server IBM Operations Planning and Control 381 HP performance data collector 424 Track 382 HP performance data managed node 425 ICAD 383 HP performance data alarm manager 426 smartsdp 384 A Remote Network Server System 427 TCP, UDP SLP, Service Location Protocol 385 IBM Application 428 OCS_CMU 386 ASA Message Router Object Def 429 OCS_AMU AppleTalk Update-based Routing Protocol 430 UTMPSD 387 UDP (AURP) 431 UTMPCD 388 TCP, UDP Unidata LDM Version 4 432 IASD Connection-less Lightweight X (CLDAP); 433 NNSP 500 Directory Access Protocol; Lightweight 434 UDP Mobile IP agent 389 TCP, UDP Directory Access Protocol (LDAP) 435 Mobile IP MN 390 UIS 436 DNA-CML 391 SynOptics SNMP Relay Port 437 comscm 392 SynOptics Port Broker Port 438 dsfgw 393 Data Interpretation System 439 dasp 394 EMBL Nucleic Data Transfer
Load more

Recommended publications
  • SILC-A SECURED INTERNET CHAT PROTOCOL Anindita Sinha1, Saugata Sinha2 Asst
    ISSN (Print) : 2320 – 3765 ISSN (Online): 2278 – 8875 International Journal of Advanced Research in Electrical, Electronics and Instrumentation Engineering Vol. 2, Issue 5, May 2013 SILC-A SECURED INTERNET CHAT PROTOCOL Anindita Sinha1, Saugata Sinha2 Asst. Prof, Dept. of ECE, Siliguri Institute of Technology, Sukna, Siliguri, West Bengal, India 1 Network Engineer, Network Dept, Ericsson Global India Ltd, India2 Abstract:-. The Secure Internet Live Conferencing (SILC) protocol, a new generation chat protocol provides full featured conferencing services, compared to any other chat protocol. Its main interesting point is security which has been described all through the paper. We have studied how encryption and authentication of the messages in the network achieves security. The security has been the primary goal of the SILC protocol and the protocol has been designed from the day one security in mind. In this paper we have studied about different keys which have been used to achieve security in the SILC protocol. The main function of SILC is to achieve SECURITY which is most important in any chat protocol. We also have studied different command for communication in chat protocols. Keywords: SILC protocol, IM, MIME, security I.INTRODUCTION SILC stands for “SECURE INTERNET LIVE CONFERENCING”. SILC is a secure communication platform, looks similar to IRC, first protocol & quickly gained the status of being the most popular chat on the net. The security is important feature in applications & protocols in contemporary network environment. It is not anymore enough to just provide services; they need to be secure services. The SILC protocol is a new generation chat protocol which provides full featured conferencing services; additionally it provides security by encrypting & authenticating the messages in the network.
    [Show full text]
  • Qos: NBAR Protocol Library, Cisco IOS XE Release 3.8S
    QoS: NBAR Protocol Library, Cisco IOS XE Release 3.8S Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax: 408 527-0883 C O N T E N T S 3COM-AMP3 through AYIYA-IPV6-TUNNELED 34 3COM-AMP3 35 3COM-TSMUX 36 3PC 37 9PFS 38 914C G 39 ACAP 40 ACAS 40 ACCESSBUILDER 41 ACCESSNETWORK 42 ACP 43 ACR-NEMA 44 ACTIVE-DIRECTORY 45 ACTIVESYNC 45 ADOBE-CONNECT 46 AED-512 47 AFPOVERTCP 48 AGENTX 49 ALPES 50 AMINET 50 AN 51 ANET 52 ANSANOTIFY 53 ANSATRADER 54 ANY-HOST-INTERNAL 54 AODV 55 AOL-MESSENGER 56 AOL-MESSENGER-AUDIO 57 AOL-MESSENGER-FT 58 QoS: NBAR Protocol Library, Cisco IOS XE Release 3.8S ii Contents AOL-MESSENGER-VIDEO 58 AOL-PROTOCOL 59 APC-POWERCHUTE 60 APERTUS-LDP 61 APPLEJUICE 62 APPLEQTC 63 APPLEQTCSRVR 63 APPLIX 64 ARCISDMS 65 ARGUS 66 ARIEL1 67 ARIEL2 67 ARIEL3 68 ARIS 69 ARNS 70 ARUBA-PAPI 71 ASA 71 ASA-APPL-PROTO 72 ASIPREGISTRY 73 ASIP-WEBADMIN 74 AS-SERVERMAP 75 AT-3 76 AT-5 76 AT-7 77 AT-8 78 AT-ECHO 79 AT-NBP 80 AT-RTMP 80 AT-ZIS 81 AUDIO-OVER-HTTP 82 AUDIT 83 AUDITD 84 AURORA-CMGR 85 AURP 85 AUTH 86 QoS: NBAR Protocol Library, Cisco IOS XE Release 3.8S iii Contents AVIAN 87 AVOCENT 88 AX25 89 AYIYA-IPV6-TUNNELED 89 BABELGUM through BR-SAT-MON 92 BABELGUM 93 BACNET 93 BAIDU-MOVIE 94 BANYAN-RPC 95 BANYAN-VIP 96 BB 97 BBNRCCMON 98 BDP 98 BFTP 99 BGMP 100 BGP 101 BGS-NSI 102 BHEVENT 103 BHFHS 103 BHMDS 104 BINARY-OVER-HTTP 105 BITTORRENT 106 BL-IDM 107 BLIZWOW 107 BLOGGER 108 BMPP 109 BNA 110 BNET 111 BORLAND-DSJ 112 BR-SAT-MON 112
    [Show full text]
  • INTERNET-DRAFT M. Ackermann Intended Status: Informational BCBS Michigan N
    INTERNET-DRAFT M. Ackermann Intended Status: Informational BCBS Michigan N. Elkins W. Jouris Inside Products Expires: April 2014 October 3, 2013 Usage of NTP for the PDM DOH IPv6 Extension Header draft-ackermann-tictoc-pdm-ntp-usage-00 Abstract The Performance and Diagnostic Metrics (PDM) Destination Options Header (DOH) for IPv6 defines metrics which are critical for timely end-to-end problem resolution, without impacting an operational production network. These metrics and their derivations can be used for network diagnostics. The base metrics are: packet sequence number and packet timestamp. The timestamp fields require time synchronization at the two end points. This document provides implementation guidelines for implementing Network Time Protocol (NTP) to provide such synchronization. Status of this Memo This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts. 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. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/1id-abstracts.html The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html Ackermann Expires April, 2014 [Page 1] INTERNET DRAFT -ackermann-tictoc-pdm-ntp-usage-00 October 2013 Copyright and License Notice Copyright (c) 2013 IETF Trust and the persons identified as the document authors.
    [Show full text]
  • Secure Internet Live Conferencing
    Einführung SILC vs. IRC vs. XMPP Architektur Nachrichten Protokoll Secure Internet Live Conferencing Frank Benkstein <[email protected]> 26.10.2007, 19:12:23h Frank Benkstein <[email protected]> Secure Internet Live Conferencing Einführung SILC vs. IRC vs. XMPP Architektur Nachrichten Protokoll Übersicht I Einführung I SILC vs. IRC vs. XMPP I Architektur I Protokoll Frank Benkstein <[email protected]> Secure Internet Live Conferencing Einführung SILC vs. IRC vs. XMPP Architektur Nachrichten Protokoll Geschichte Geschichte 1996 Idee und Entwurf durch Pekka Riikonen 1997 erster Code 1998 Rewrite in C++ 1999 Rewrite in C 2000 erste Veröffentlichung der Quelltexte Einreichung der Spezifikationen bei der IETF 2003 SILC-Client 1.0 Frank Benkstein <[email protected]> Secure Internet Live Conferencing Einführung SILC vs. IRC vs. XMPP Architektur Nachrichten Protokoll Design Ziele I Echtzeit-Text-Kommunikation I Viele-Zu-Viele (ähnlich IRC) I Eins-Zu-Eins (Instant Messaging) I Multimedia-Fähigkeit I Datei-Transfer I Sicherheit I Modularität Frank Benkstein <[email protected]> Secure Internet Live Conferencing Einführung SILC vs. IRC vs. XMPP Architektur Nachrichten Protokoll Protokoll-Eigenschaften Protokoll-Eigenschaften I Verschlüsselung I gesamte Kommunikation verschüsselt und authentifiziert I unverschlüsselte Kommunikation unmöglich* I Signatur von Nachrichten I Unicode (UTF-8) statt ASCII I Nicknames I Channel-Namen I Nachrichten I Peer-to-Peer für Dateitransfer I alles andere über Server Frank Benkstein <[email protected]> Secure Internet Live Conferencing Einführung SILC vs. IRC vs. XMPP Architektur Nachrichten Protokoll Protokoll-Eigenschaften Clients I eindeutige Client-ID I Nicknamen I nicht eindeutig* I UTF-8 I bis zu 128 Bytes (!) lang I gleicher Public-Key möglich Frank Benkstein <[email protected]> Secure Internet Live Conferencing Einführung SILC vs.
    [Show full text]
  • Which Time Server Option Is Best for Synchronizing Your Clocks
    WHICH TIME SERVER OPTION IS BEST FOR SYNCHRONIZING YOUR CLOCKS? Any electronic device that automatically displays REGARDING MASTER the current local time – your clocks, phone, tablet, TIME CONTROLLERS computer and even most TVs – has to pull that time from a time server. AND The time server acts as a messenger of sorts; IP NETWORK CLOCKS it reads the time from a reference clock and distributes that information via a computer network (ETHERNET OR WI-FI) to your device when the device requests it. The time server could be a local network time server or an internet time server. SNTP, or Simple Network Time Protocol, is an internet standard protocol that allows a clock or device to contact a server and get the current time. It’s a simplification of the more robustNTP (Network Time Protocol) and is used in most embedded devices and computers. Once the device receives the current Coordinated Universal Time (UTC), the device applies offsets such as time zone or daylight saving time considerations, as well as the time spent on the network retrieving the time, before displaying the accurate local time. January 2018 AMERICAN TIME WHITE PAPER BY: MAX BLOM When it comes to syncing time for your organization’s clocks, you have 3 options: Let’s take a look at how each of these options work, their pros and cons, and our recommendation. Port 123 is reserved specifically for External Server IP Address NTP/SNTP communication 1 The NIST – the U.S. Department of Commerce’s National Institute of Standards and Technology – is the primary source for synchronizing time systems in the U.S.
    [Show full text]
  • Endrun TECHNOLOGIES Præcis Cntp Network Time Server
    Smarter Timing Solutions EndRun TECHNOLOGIES Præcis Cntp Network Time Server User’s Manual Præcis Cntp Network Time Server User’s Manual EndRun Technologies 1360 North Dutton Avenue #200 Santa Rosa, California USA 95401 Phone 707-573-8633 • Fax 707-573-8619 Preface Thank you for purchasing the Præcis Cntp Network Time Server. Our goal in developing this product is to bring precise, Universal Coordinated Time (UTC) into your network quickly, easily and reliably. Your new Præcis Cntp is fabricated using the highest quality materials and manufacturing processes available today, and will give you years of troublefree service. About EndRun Technologies Founded in 1998 and headquartered in Santa Rosa, California, we are the leaders in the exciting new time and frequency distribution technology based on the Code Division Multiple Access (CDMA) mobile telecommunications infrastructure. Our innovative designs and painstaking attention to the details of efficient manufacturability have made us the first to bring this technology to the broad synchronization market at prices small businesses can afford. EndRun Technologies markets this technology in three major product lines: Network Time Sources/Servers – These units are configured for optimum performance in operation with network servers/networks running the Internet protocol known as the Network Time Protocol (NTP). Instrumentation Time and Frequency References – These products provide UTC traceable time and frequency signals for use in precision test and measurement instrumentation. OEM Time and Frequency Engines – These products provide the core time and frequency capabilities to our customers who require lower cost and tighter integration with their own products. About this manual This manual will guide you through simple installation and set up procedures.
    [Show full text]
  • A Framework for Designing Cryptographic Key Management Systems
    NIST Special Publication 800-130 A Framework for Designing Cryptographic Key Management Systems Elaine Barker Miles Smid Dennis Branstad Santosh Chokhani C O M P U T E R S E C U R I T Y NIST Special Publication 800-130 A Framework for Designing Cryptographic Key Management Systems Elaine Barker Computer Security Division Information Technology Laboratory Miles Smid Orion Security Solutions Silver, Spring, MD Dennis Branstad NIST Consultant Austin, TX Santosh Chokhani Cygnacom McLean, VA August 2013 U.S. Department of Commerce Penny Pritzker, Secretary National Institute of Standards and Technology Patrick D. Gallagher, Under Secretary of Commerce for Standards and Technology and Director SP 800-130 August 2013 Authority This publication has been developed by NIST to further its statutory responsibilities under the Federal Information Security Management Act (FISMA), Public Law (P.L.) 107-347. NIST is responsible for developing information security standards and guidelines, including minimum requirements for Federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate Federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130, Section 8b(3), Securing Agency Information Systems, as analyzed in Circular A-130, Appendix IV: Analysis of Key Sections. Supplemental information is provided in Circular A-130, Appendix III, Security of Federal Automated Information Resources. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on Federal agencies by the Secretary of Commerce under statutory authority.
    [Show full text]
  • NBAR2 Standard Protocol Pack 1.0
    NBAR2 Standard Protocol Pack 1.0 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax: 408 527-0883 © 2013 Cisco Systems, Inc. All rights reserved. CONTENTS CHAPTER 1 Release Notes for NBAR2 Standard Protocol Pack 1.0 1 CHAPTER 2 BGP 3 BITTORRENT 6 CITRIX 7 DHCP 8 DIRECTCONNECT 9 DNS 10 EDONKEY 11 EGP 12 EIGRP 13 EXCHANGE 14 FASTTRACK 15 FINGER 16 FTP 17 GNUTELLA 18 GOPHER 19 GRE 20 H323 21 HTTP 22 ICMP 23 IMAP 24 IPINIP 25 IPV6-ICMP 26 IRC 27 KAZAA2 28 KERBEROS 29 L2TP 30 NBAR2 Standard Protocol Pack 1.0 iii Contents LDAP 31 MGCP 32 NETBIOS 33 NETSHOW 34 NFS 35 NNTP 36 NOTES 37 NTP 38 OSPF 39 POP3 40 PPTP 41 PRINTER 42 RIP 43 RTCP 44 RTP 45 RTSP 46 SAP 47 SECURE-FTP 48 SECURE-HTTP 49 SECURE-IMAP 50 SECURE-IRC 51 SECURE-LDAP 52 SECURE-NNTP 53 SECURE-POP3 54 SECURE-TELNET 55 SIP 56 SKINNY 57 SKYPE 58 SMTP 59 SNMP 60 SOCKS 61 SQLNET 62 SQLSERVER 63 SSH 64 STREAMWORK 65 NBAR2 Standard Protocol Pack 1.0 iv Contents SUNRPC 66 SYSLOG 67 TELNET 68 TFTP 69 VDOLIVE 70 WINMX 71 NBAR2 Standard Protocol Pack 1.0 v Contents NBAR2 Standard Protocol Pack 1.0 vi CHAPTER 1 Release Notes for NBAR2 Standard Protocol Pack 1.0 NBAR2 Standard Protocol Pack Overview The Network Based Application Recognition (NBAR2) Standard Protocol Pack 1.0 is provided as the base protocol pack with an unlicensed Cisco image on a device.
    [Show full text]
  • IBM Z Server Time Protocol Guide
    Front cover Draft Document for Review August 3, 2020 1:37 pm SG24-8480-00 IBM Z Server Time Protocol Guide Octavian Lascu Franco Pinto Gatto Gobehi Hans-Peter Eckam Jeremy Koch Martin Söllig Sebastian Zimmermann Steve Guendert Redbooks Draft Document for Review August 3, 2020 7:26 pm 8480edno.fm IBM Redbooks IBM Z Server Time Protocol Guide August 2020 SG24-8480-00 8480edno.fm Draft Document for Review August 3, 2020 7:26 pm Note: Before using this information and the product it supports, read the information in “Notices” on page vii. First Edition (August 2020) This edition applies to IBM Server Time Protocol for IBM Z and covers IBM z15, IBM z14, and IBM z13 server generations. This document was created or updated on August 3, 2020. © Copyright International Business Machines Corporation 2020. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Draft Document for Review August 3, 2020 8:32 pm 8480TOC.fm Contents Notices . vii Trademarks . viii Preface . ix Authors. ix Comments welcome. .x Stay connected to IBM Redbooks . xi Chapter 1. Introduction to Server Time Protocol . 1 1.1 Introduction to time synchronization . 2 1.1.1 Insertion of leap seconds . 2 1.1.2 Time-of-Day (TOD) Clock . 3 1.1.3 Industry requirements . 4 1.1.4 Time synchronization in a Parallel Sysplex. 6 1.2 Overview of Server Time Protocol (STP) . 7 1.3 STP concepts and terminology . 9 1.3.1 STP facility . 9 1.3.2 TOD clock synchronization .
    [Show full text]
  • Introduction to Public Key Infrastructures
    Introduction to Public Key Infrastructures Johannes A. Buchmann • Evangelos Karatsiolis Alexander Wiesmaier Introduction to Public Key Infrastructures 123 Johannes A. Buchmann Evangelos Karatsiolis FB Informatik FlexSecure GmbH TU Darmstadt Darmstadt Darmstadt Germany Germany Alexander Wiesmaier AGT International Darmstadt Germany ISBN 978-3-642-40656-0 ISBN 978-3-642-40657-7 (eBook) DOI 10.1007/978-3-642-40657-7 Springer Heidelberg New York Dordrecht London Library of Congress Control Number: 2013954524 © Springer-Verlag Berlin Heidelberg 2013 This work is subject to copyright. All rights are reserved by the Publisher, whether the whole or part of the material is concerned, specifically the rights of translation, reprinting, reuse of illustrations, recitation, broadcasting, reproduction on microfilms or in any other physical way, and transmission or information storage and retrieval, electronic adaptation, computer software, or by similar or dissimilar methodology now known or hereafter developed. Exempted from this legal reservation are brief excerpts in connection with reviews or scholarly analysis or material supplied specifically for the purpose of being entered and executed on a computer system, for exclusive use by the purchaser of the work. Duplication of this publication or parts thereof is permitted only under the provisions of the Copyright Law of the Publisher’s location, in its current version, and permission for use must always be obtained from Springer. Permissions for use may be obtained through RightsLink at the Copyright Clearance Center. Violations are liable to prosecution under the respective Copyright Law. The use of general descriptive names, registered names, trademarks, service marks, etc. in this publication does not imply, even in the absence of a specific statement, that such names are exempt from the relevant protective laws and regulations and therefore free for general use.
    [Show full text]
  • Encryption Is Futile: Delay Attacks on High-Precision Clock Synchronization 1
    R. ANNESSI, J. FABINI, F.IGLESIAS, AND T. ZSEBY: ENCRYPTION IS FUTILE: DELAY ATTACKS ON HIGH-PRECISION CLOCK SYNCHRONIZATION 1 Encryption is Futile: Delay Attacks on High-Precision Clock Synchronization Robert Annessi, Joachim Fabini, Felix Iglesias, and Tanja Zseby Institute of Telecommunications TU Wien, Austria Email: fi[email protected] Abstract—Clock synchronization has become essential to mod- endanger control decisions, and adversely affect the overall ern societies since many critical infrastructures depend on a functionality of a wide range of (critical) services that depend precise notion of time. This paper analyzes security aspects on accurate time. of high-precision clock synchronization protocols, particularly their alleged protection against delay attacks when clock syn- In recent years, security of clock synchronization received chronization traffic is encrypted using standard network security increased attention as various attacks on clock synchronization protocols such as IPsec, MACsec, or TLS. We use the Precision protocols (and countermeasures) were proposed. For this Time Protocol (PTP), the most widely used protocol for high- reason, clock synchronization protocols need to be secured precision clock synchronization, to demonstrate that statistical whenever used outside of fully trusted network environments. traffic analysis can identify properties that support selective message delay attacks even for encrypted traffic. We furthermore Clock synchronization protocols are specifically susceptible to identify a fundamental conflict in secure clock synchronization delay attacks since the times when messages are sent and between the need of deterministic traffic to improve precision and received have an actual effect on the receiver’s notion of the need to obfuscate traffic in order to mitigate delay attacks.
    [Show full text]
  • Ipv6-Security Monitoring
    Security Monitoring ITU/APNIC/MICT IPv6 Security Workshop 23rd – 27th May 2016 Bangkok Last updated 22 July 2014 1 Managing and Monitoring IPv6 Networks p SNMP Monitoring p IPv6-Capable SNMP Management Tools p NetFlow Analysis p Syslog p Keeping accurate time p Intrusion Detection p Managing the Security Configuration 2 Using SNMP for Managing IPv6 Networks 3 What is SNMP? p SNMP – Simple Network Management Protocol p Industry standard, hundreds of tools exist to exploit it p Present on any decent network equipment p Query/response based: GET / SET p Monitoring generally uses GET p Object Identifiers (OIDs) p Keys to identify each piece of data p Concept of MIB (Management Information Base) p Defines a collection of OIDs What is SNMP? p Typical queries n Bytes In/Out on an interface, errors n CPU load n Uptime n Temperature or other vendor specific OIDs p For hosts (servers or workstations) n Disk space n Installed software n Running processes n ... p Windows and UNIX have SNMP agents What is SNMP? p UDP protocol, port 161 p Different versions n v1 (1988) – RFC1155, RFC1156, RFC1157 p Original specification n v2 – RFC1901 ... RFC1908 + RFC2578 p Extends v1, new data types, better retrieval methods (GETBULK) p Used is version v2c (simple security model) n v3 – RFC3411 ... RFC3418 (w/security) p Typically we use SNMPv2 (v2c) SNMP roles p Terminology: n Manager (the monitoring station) n Agent (running on the equipment/server) How does it work? p Basic commands n GET (manager → agent) p Query for a value n GET-NEXT (manager → agent) p Get next value (e.g.
    [Show full text]