Power Systems Monitoring and Control using Telecom Network Management Standards

Historically, different solutions have been developed for power systems control and telecommunications network management environments. The former was characterized by proprietary solutions, while the latter has been involved for years in a strong standardization process guided by criteria of openness. Today, power systems control standardization is in progress, but it is at an early stage compared to the telecommunications management area, especially in terms of information modeling. Today, control equipment tends to exhibit more computational power, and communication lines have increased their performance. These trends hint at some conceptual convergence between power systems and telecommunications networks from a management perspective. This convergence leads us to suggest the application of well-established telecommunications management standards for power systems control. This paper shows that this is a real medium-to-long term possibility

Virtual harm reduction efforts for Internet gambling: effects of deposit limits on actual Internet sports gambling behavior

Background: In an attempt to reduce harm related to gambling problems, an Internet sports betting service provider, bwin Interactive Entertainment, AG (bwin), imposes limits on the amount of money that users can deposit into their online gambling accounts. We examined the effects of these limits on gambling behavior. Methods: We compared (1) gambling behavior of those who exceeded deposit limits with those who did not, and (2) gambling behavior before and after exceeding deposit limits. We analyzed 2 years of the actual sports gambling behavior records of 47000 subscribers to bwin. Results: Only 160 (0.3%) exceeded deposit limits at least once. Gamblers who exceeded deposit limits evidenced higher average number of bets per active betting day and higher average size of bets than gamblers who did not exceed deposit limits. Comparing the gambling behavior before and after exceeding deposit limits revealed slightly more unfavorable gambling behavior after exceeding deposit limits. Conclusion: Our findings indicate that Internet gamblers who exceed deposit limits constitute a group of bettors willing to take high risks; yet, surprisingly, they appear to do this rather successfully because their percentage of losses is lower than others in the sample. However, some of these gamblers exhibit some poor outcomes. Deposit limits might be necessary harm reduction measures to prevent the loss of extremely large amounts of money and cases of bankruptcy. We discuss how these limits might be modified based on our findings

The Push Model in Web-Based Network Management

The management of IP networks is currently based on the SNMP protocol, and the use of expensive network management platforms designed according to the manager/agent paradigm of the SNMP framework. It uses two different schemes to transfer management data: a request/response protocol for data collection and network monitoring (data polling), and unsolicited push to deliver SNMP notifications. This design is exposed to a number of problems, with regards to the time-to-market of vendor-specific management software, versioning, protocol efficiency, security, etc. In this paper, we propose a novel approach to network management based on the push model. This model is well-known in software engineering, and encountered a large success on the Web recently with the push technologies. It relies on the publish/subscribe/distribute paradigm, and uses a single scheme to transfer all management data. We describe why it is more efficient, in terms of network and systems resources, than the traditional pull model. We also explain in detail how to implement this model with Web technologies to deliver SNMP notifications, to handle events, and to distribute MIB data for network monitoring and data collection

Development of a Network Monitoring System for Ship's Network Security Using SNMP

Nowadays, the risk of unauthorized access or malicious attacks on ship’s systems onboard internally or externally is possible to be a threat to the safe operation of ship’s network. According to the requirements of IEC (International Electro-Technical Commission) 61162-460 network standard, a secure 460-Network is designed for safety and security of networks on board ships and developed a network monitoring software application for monitoring the 460-Network. Therefore, in this thesis to secure the ship’s network, ship’s security network is designed and implemented by using 460-Switch, 460-Nodes, 460-gateway that contains firewalls and DMZ (Demilitarized Zone) with various security application servers in compliance with IEC 61162-460. Also, 460-firewall is used to permit/deny traffic to/from unauthorized networks. 460-NMS (Network Monitoring System) is a network monitoring software application, developed by using SNMP (Simple Network Management Protocol) SharpNet library with.Net 4.5 frameworks and backhand SQLite database management which are used to manage the network information. 460-NMS configures 460-Switch and communicates by SNMP, SNMP Trap, and Syslog to gather the network information and status of each 460-Switch interface. 460-NMS analyze and monitors the 460-Network load, traffic flow, current system status, network failure, or detect unknown device connection. It notifies the system administrator via alarms, notifications or warnings in case if any network problem occurs. To confirm the performance of the designed 460-Network according to the requirements of IEC 61162-460 standard: First, the laboratory is composed of the dedicated network with CISCO 460-Switch, 460-Gateway, Fortigate 460-Firewall, and lab computers. These network devices exclude from external networks such as the internet. The 460-NMS is connected with configured laboratory network to analyze and monitor the network traffic flow, load and device connections by using SNMP. Second, the test of 460-NMS is carried out in a company’s network. That is very complex network environment which includes IEC 61162-460, IEC 61162-450, IEC 61162-3 (NMEA 2000), IEC 61162-1, -2 (NMEA 0183) data networks with 450-Gateway, Gateway 450 to 0183, Gateway N2K to 0183, and Gateway 0183 to N2K and excludes from unauthorized networks. Finally after testing, it is confirmed that the 460-NMS analyzes, monitors the whole 460-network and notifies and warns abnormal status of 460-network as the requirements of IEC 61162-460 international standards.ABSTRACT IX 1. INTRODUCTION 1 1.1 MOTIVATION 1 1.2 STUDY IDEA 4 2. INTERNATIONAL STANDARDS OF SHIP NETWORK 5 2.1 OVERVIEW 5 2.2 SHIP’S DATA NETWORK 7 2.3 IEC 61162-1, IEC 61162-2, NMEA 0183 8 2.4 IEC 61162-3, NMEA 2000 10 2.4.1 CAN 11 2.4.2 NMEA 2000 Messages 12 2.5 IEC 61162-450 14 2.5.1 Function Blocks 15 2.5.2 IEC 61162-450 Message 16 2.5.3 IEC 61162-1 sentence 17 2.6 IEC61162-460 18 2.6.1 Objectives 18 2.6.2 Scope 19 3. 460-NETWORK REQUIREMENTS 21 3.1 OVERVIEW 21 3.1.1 Network Components 21 3.2 460-NETWORK TRAFFIC MANAGEMENT REQUIREMENTS 24 3.2.1 460-Node Requirements 24 3.2.2 460-Switch Requirements 25 3.3 SECURITY REQUIREMENTS 26 3.3.1 Threat Scenarios 26 3.3.2 Internal Network Security Requirements 29 3.3.3 Uncontrolled Network security requirements 30 3.4 460-GATEWAY REQUIREMENTS 32 3.5 IEC 61162 460-NMS REQUIREMENTS 34 3.5.1 460-Node 34 3.5.2 460-Switch 34 3.5.3 Network load-monitoring requirements 35 3.5.4 Syslog recording function requirements 36 3.5.5 SNMP requirements 37 4. 460-GATEWAY DESIGN AND SNMP 38 4.1 SNMP 38 4.1.1 SNMP Components 38 4.1.2 SNMP Versions 39 4.1.3 MIB 41 4.1.4 Syslog 44 4.2 CISCO SWITCH 49 4.2.1 Initial configuration for the Switch 50 4.2.2 IP Configuration 52 4.2.3 SNMP Configuration 53 4.2.4 Syslog Configuration 54 4.3 IEC 61162-460-GATEWAY DESIGN AND 460-NETWORK CONFIGURE 55 5. DESIGN OF A 460-NMS 58 5.1 460-NMS ARCHITECTURE 59 5.2 460-NMS DESIGN AND TOOLS 61 5.2.1 Application Interface 61 5.2.2 Database 62 5.2.3 Backhand developing 62 5.3 ENTITY—RELATIONSHIP DIAGRAMS (ERD) MODEL OF 460-NMS 63 5.4 TRAFFIC FLOW INFORMATION LISTS OF 460-NMS 64 5.5 SNMP MIB DATA PARSING 66 5.5.1 SNMP message parsing 68 5.5.2 SNMP Trap 69 5.5.3 Syslog Parsing 69 6. IMPLEMENTATION AND TESTING OF 460-NMS 70 6.1 460-NMS INTERFACE 70 6.1.1 Login Wizard 70 6.1.2 Main Form 70 6.2 460-NMS TESTING 72 6.2.1 Lab Test 72 6.3 REAL NETWORK TEST 78 7. CONCLUSION 87 REFERENCES 88 APPENDIX 91 1. INFORMATION LIST OF 460-NMS DATABASE 91 2. SYSLOG MESSAGE 94 3. SNMP VERSIONS 96 4. SNMP MESSAGE 97Maste

The SNMP evolution: lost on simplicity or on functionality

The SNMP framework has gained a new stimulus with the efficient emergence of the third version (SNMPv3). Beyond its enrichments, namely the security model, the enormous base of legacy knowledge and legacy systems leads the SNMP management framework to a necessary choice in nowadays management scenarios. However, its services correspond roughly to low-level operations for setting or retrieving network equipment parameters. Traditionally, high-level management operations were outside the scope of IETF strategy. The IETF Distributed Management working group have been producing normalization documents that intent to apply to the enrichment of SNMP semantics, especially in what concerns the processing of management information. One of such deliverables is the Expression MIB that, up till now, is in the Internet draft standard track. This paper will highlight the recent outcome of this WG, will present an Expression MIB implementation and will discuss the cost of these more powerful solutions on the “keep simple” and “low inference” principles of SNMP engines

An Assessment of Practical Hands-On Lab Activities in Network Security Management

With the advancement in technology over the past decades, networks have become increasingly large and complex. In the meantime, cyberattacks have become highly sophisticated making them difficult to detect. These changes make securing a network more challenging than ever before. Hence, it is critical to prepare a comprehensive guide of network security management for students assist them in becoming network security professionals. The objective of this paper is to introduce a variety of techniques related to network security management, such as Simple Network Management Protocol (SNMP), event management, security policy management, risk management, access control, and remote monitoring. With the usage of these techniques, malicious activities from outsiders and misuse by insiders can be effectively monitored and managed. A network learning environment is proposed for students to practice network security management experiments. In addition, hands-on lab exercises are suggested. These activities will help students become familiar with the operations of network security management and allow them to further apply practical skills to protect networks

JAMAP: a Web-Based Management Platform for IP Networks

In this paper, we describe JAMAP, a prototype of a Web-based management platform for IP networks. It is entirely written in Java. It implements the push model to perform regular management (permanent network monitoring and data collection) and ad hoc management (temporary network monitoring and troubleshooting). The communication between agents and managers relies on HTTP transfers between Java applets and servlets over persistent TCP connections. The SNMP MIB data is encapsulated in serialized Java objects that are transmitted as MIME parts via HTTP. The manager consists of two parts: the management server, a static machine that runs the servlets, and the management station, which can be any desktop running a Web browser. The MIB data is transparently compressed with gzip, which saves network bandwidth without increasing latency too significantly

JAMAP: a Web-Based Management Platform for IP Networks

In this paper, we describe JAMAP, a prototype of Web-based management platform for IP networks. It is entirely written in Java. It implements the push model to perform regular management (i.e. permanent network monitoring and data collection) and ad hoc management (i.e. temporary network monitoring and troubleshooting). The communication between agents and managers relies on HTTP transfers between Java applets and servlets over persistent TCP connections. The SNMP MIB data is encapsulated in serialized Java objects that are transmitted as MIME parts via HTTP. The manager consists of two parts: the management server, a static machine that runs the servlets, and the management station, which can be any desktop running a Web browser. The MIB data is transparently compressed with gzip, which saves network bandwidth without increasing latency too significantly