Introduction

The network scenario of the current case design can be implemented in the current project scenario and the network topological designs according to the case scenario of “Bank of Adelaide” or BOA can be developed including the “local area network” or LAN design. In addition to that, various network designs can be reviewed based on the case scenario in order to provide the network design between the branches of the bank scenario. The bank is a mainland bank of Australia and has several branches that can be interconnected through proper implementation of the network design using a valid topological structure. Mitigation from the attacks like DDoS and ransomware can be provided based on the adopted network design and the intranet of the brunches of BOA. The network design must be acquired in a way that the ransomware and DDoS attacks can not be applicable in the brunches of Melbourne and Sydney. The main branch of the bank, BOA, in Australia, must be adopted with a proper VPN implementation in order to prevent the IP tracking of the brunches and that can be implemented to the privacy concerns of the users and employees of the bank as per the requirements of the project. In this scenario, the hardware implementation can be deployed to the network design and the intranet between the brunches as per the requirements of the project.

Network Topology

In this section, the network topology of the brunches and the main branch of BOA can be implemented based on the network design. The topological structure can be implemented based on the case scenario that can be equipped from the project overview. The network branches of the bank can be defined as four sub-branches and the main branch of BOA as per the case scenario. On the other hand, the description of the topological structure can be described as a star topology (Birkinshaw et al., 2019). The justification for using such a topology can be discussed in this section in order to provide a generic view of the network design. In addition to that, the model implementation is based on the bank scenario in all four branches including the main brunch alongside the topological that has been provided. On the other hand, the topology can be discussed with the aspects of starting topology as per the requirements of the project. In addition to that, the described topology can be adopted in order to terminate the aspects of network security and intranet of the bank branches.

Figure 1: Network topology diagram

(Source: Created by the learner)

The above diagram can be referred to as the network topology diagram as per the requirements of the project. The start topology has been adopted in order to proceed with the designing of the network of LAN design based on the case scenario.

LAN Design

The LAN design and the adopted topology for each subnet can be discussed alongside the design aspect of each subnet as per the requirements of the project. In addition to that, each configuration of the LAN alongside the subnets can be discussed based on the network design. The connection of the intranet as well as the internet between the subnets of the sub-branches can be applied and the server connection of each regional branch can be described as per the requirements. The topological structure that has been adopted is star topology in each subnet address related to the regional banks of the main branch of BOA.

Figure 2: Sydney branch configuration

(Source: Self-created at Cisco)

The configuration of the LAN to the Sydney branch has been implemented in this section alongside the topological implementation (Umar et al., 2021). The topology that has been acquired is star topology in order to develop the network design and that can be implemented to the IP address configuration as per the requirements of the project.

Figure 3: Melbourne branch configuration

(Source: Self-created at Cisco)

The above figure can be referred to as the LAN structure of Melbourne and that can be applied to the Ip address configuration based on the case scenario of the BOA as per the requirements.

Figure 4: Brisbane branch configuration

(Source: Self-created at Cisco)

The implementation is based on the topological structure that can be implemented in this section to ptovde the desired intranet of the local area network.

Figure 5: Parth (main branch) branch configuration

(Source: Self-created at Cisco)

The above figure can be referred to as the topological structure of the local area network of the main branch as required.

IP Addressing

Figure 6: Pc0 IP configuration

(Source: Self-created at Cisco)

Figure 7: Pc1 IP configuration

(Source: Self-created at Cisco)

Figure 8: Pc2 IP configuration

(Source: Self-created at Cisco)

Figure 9: Pc3 IP configuration

(Source: Self-created at Cisco)

Figure 10: Pc4 IP configuration

(Source: Self-created at Cisco)

Figure 11: Pc5 IP configuration

(Source: Self-created at Cisco)

Figure 12: Pc6 IP configuration

(Source: Self-created at Cisco)

Figure 13: Pc7 IP configuration

(Source: Self-created at Cisco)

Figure 14: Pc8 IP configuration

(Source: Self-created at Cisco)

Figure 15: Pc9 IP configuration

(Source: Self-created at Cisco)

Figure 16: Pc10 IP configuration

(Source: Self-created at Cisco)

Figure 17: Pc11 IP configuration

(Source: Self-created at Cisco)

Figure 18: Server3 Vlan connections

(Source: Self-created at Cisco)

Figure 19: Server3 configuration status

(Source: Self-created at Cisco)

Figure 20: FastEthernet connection set up

(Source: Self-created at Cisco)

Figure 21: Main Router configuration and securing the host with password

(Source: Self-created at Cisco)

Figure 22: Network Interface summary

(Source: Self-created at Cisco)

Figure 23: Giving specific password for the server

(Source: Self-created at Cisco)

Figure 24: configuration successful

(Source: Self-created at Cisco)

SYDNEY
Total user	80000
Magic Number	131072
useful host	131070
n	17
CIDR	15
Subnet Mask	255.254.0.0
Network IP	12.74.0.0
First Host IP address	12.74.0.1
Last IP address	12.75.255.255
broadcast IP	12.75.255.255
Reverse subnet mask	0.1.255.255
Last host IP address	12.75.255.254
Usable host IP range	12.74.0.1-12.75.255.254

As per the above table, all the necessary calculations are made in order to know the range of the IP addresses. This is mentionable that, the value of the n is 17 and if the calculations are made the 2ⁿ is equals to 2¹⁷ and that means 131072. This represents the value of magic number is 131072. Useful host should be always 2 less than the magic number and the value is 131070. The subnet mask is 255.254.0.0 while the network ip is 12.74.0.1

Users	IP address
1	12.74.0.1
2	12.74.0.2
3	12.74.0.3
4	12.74.0.4
5	12.74.0.5
6	12.74.0.6
7	12.74.0.7
8	12.74.0.8
9	12.74.0.9
10	12.74.0.10
11	12.74.0.11
12	12.74.0.12
13	12.74.0.13
14	12.74.0.14
15	12.74.0.15
16	12.74.0.16
17	12.74.0.17
18	12.74.0.18
19	12.74.0.19
20	12.74.0.20
21	12.74.0.21
22	12.74.0.22

Network security research and issues

The implementation network implementation is based on the prevention of mentioned attacks as per the overview of the project. In addition to that,

Figure 25: Pinging in command prompt

(Source: Self-created at Cisco)

Figure 26: Going inside the web browser

(Source: Self-created at Cisco)

Figure 27: opening with the url

(Source: Self-created at Cisco)

Figure 28: Setting up the mitigation

(Source: Self-created at Cisco)

Figure 29: Setting up SSH

(Source: Self-created at Cisco)

Figure 30: Internal set up of for DDoS mitigation

(Source: Self-created at Cisco)

Figure 29: Setting up the protocol

(Source: Self-created at Cisco)

Figure 30: Mitigation successful

(Source: Self-created at Cisco)

Figure 31: Pinging is showing request timed out

(Source: Self-created at Cisco)

Figure 31: Exhibiting the used protocol

(Source: Self-created at Cisco)

As seen from the above figure, user protocols can be seen. This is mentionable that, for the mitigation of the DDoS and ransomware attacks specific code has been used. Under that scenario, the protection gets successful to the targeted server as that can refuse entering inside the local host. As per the requirement, By enabling the firewall, the mitigation can be done with ease.

Figure 31:Ip address brief

(Source: Self-created at Cisco)

Hardware

The hardware implementation is based on the network design of the bank scenario. The LAN design of each subnet can be referred to in this section in order to review the components or the tools of the network design that has been implemented in the software environment Cisco (Prasad et al., 2022). In addition to that, the devices of the interconnection can be defined as routers, servers, computers, switches, firewalls, and more based on the connection. The components that have been mentioned can be referred to as LAN design and the simulation of the packets. There are various components in the Cisco software environment in order to proceed with the network design aligned to the case scenario of the BOA bank intranet.

Conclusion

The implementation of the network design of the intranet alongside the connectivity of the intranet has been developed and can be referred to as the LAN design and the implemented topology of each branch. In addition to that, the implementation of the network topology of the subnets of each local area network has been developed and deployed in order to deliver the intranet connection between the servers of each branch. On the other hand, the mitigation of various cyber attacks like ransomware attacks and DDoS attacks has been implemented in the configuration of the IP address as per the requirements of the project. The implementation of the network design, based on the case scenario, can be discussed in further studies in order to study the aspect of the attacks based on the nature of the attacks.

In the recommendation part, it can be stated that the implementation of the host attacks from various malpractices can be prevented. The servers can be defined by connecting to the victim or host server to proceed with the mitigation of the attacks. The prevention aspects of the attacks have been developed and reviewed throughout the project and further adaptation on the mitigation part can be acquired from the essence of the current project. The prevention of the attacks can be tested on the host server as expected and the mitigation stages and methods can be acquired in future studies of bank privacy and security.

Reference

Birkinshaw, C., Rouka, E. and Vassilakis, V.G., 2019. Implementing an intrusion detection and prevention system using software-defined networking: Defending against port-scanning and denial-of-service attacks. Journal of Network and Computer Applications, 136, pp.71-85.

Umar, R., Riadi, I. and Kusuma, R.S., 2021. Mitigating sodinokibi ransomware attack on cloud network using software-defined networking (SDN). International Journal of Safety and Security Engineering, 11(3), pp.239-246.

Prasad, S., Prasad, A., Arockiasamy, K. and Yuan, X., 2022. Emulation and Analysis of Software-Defined Networks for the Detection of DDoS Attacks. In International Conference on Computer, Communication, and Signal Processing (pp. 213-231). Springer, Cham.