Josue Durosier

Diligent and motivated recent graduate with a strong foundation in cybersecurity seeking to leverage academic achievements and passion for technology to contribute effectively in a cybersecurity IT role. Possesses a solid understanding of security principles, protocols, and technologies gained through coursework and hands-on projects. Eager to apply theoretical knowledge in a practical setting and committed to continuous learning in the dynamic field of cybersecurity.

• Comptia Security +

Candidate ID : COMP001022256643

EXP Date: May 25, 2026

Computer Networking Project | New Jersey Institute of Technology

• In this scenario i was a junior network task with setting up a WAN for a mock bank that includes three LANs (where one would partitioned by three VLANs), and configure all network devices and endpoints to communicate with entire WAN. The network design consisted of three offices with three routers connecting them. The first office had two switches and six endpoints devices while the other two offices only had one switch a piece and both only had three endpoints.
• The first task I was given a network address that i ad to divide into 8 subnets that would later be used for all network devices and endpoints.
• The second task was done in office 1 where i create four new VLANs, VLAN 10 Management, VLAN 20 Marketing , VLAN 30 Accounting and VLAN 100 Native which is where we change the default native VLAN to. Then i configured the interfaces on the switch to be in access mode and assigned FastEthernet0/1-10 to VLAN 10, FastEthernet0/11-20 to VLAN 20 and FastEthernet0/21-24 to VLAN 30. Afterwards i set the interconnecting link between the two switches in office 1 to trunk then disabled DTP on the access ports of both switches
• Task three was to simply assign the proper ip address to each network devices and endpoint using the subnet table created in the first task
• The Fourth assignment was to configure the first router for inter-VLAN routing to allow the different VLANS from office to be able to communicate with each other
• The Fifth Task had me secure the switches physical ports. I enabled port security on the access ports that were connected to end devices, secured Authorized MAC addresses using sticky learning, then finally disabled all unused ports.
• The sixth assignment had me configure all the router with OSPF to allow all subnets to communicate.
• Next I configured ACLs on the Router 3 to prevent unauthorized access to the NTP/Syslog server
• with the eighth task i set up basic security setting on all network devices. First with a Username and password for the console line, then securing privileged mode with a password as well as encrypting all passwords on the devices.
• The final task of the project had me Configure SSHv2 services on all router to allow for remote administration

Microsoft Azure Sentinel Lab

• The purpose of this lab is to monitor attacks on a honeypot virtual machine using Azure sentinel and a log repository, as well as get the geolocation of those IP addresses
• I first named the virtual machine and the resource group that it would belong to, then set a username and password. Next i went over to the networking settings of the vm and the change the NIC network security group settings, which is essential a firewall. I deleted the old rule and created one that left all destination ports open to any protocol with an allow action. Then i deployed the vm.
• Afterwards i went and created a log analytics work space that would be able to ingest logs from my honeypot. I named the log and put it in the same resource group as my honey pot. Then i went to the security center where i turned on defender and enabled the ability for my workspace to get the logs of all events. While going into the workspaces data sources where i found the vm i created and connected it.
• Next i began the set up process for azure sentinel after creation. The first thing is to select the log analytics workspace that you want to connect to and add it to the SIEM.
• Now I grabbed the IP address of the honeypot that i created and use Remote Desktop connection app on my host computer to connect to the honeypot. After signing in and doing usual windows 10 start up settings, i went to the windows firewall and the properties to turn off the firewall state. This will allow my vm to be discovered quicker on the internet.
• Then i went to GitHub where i got a powershell script that would be able to grab logon data from event viewer take the Ip address of failed logon attempt then output the geolocation to a log file. I had to sign up for an account at ipgeolocation.io to get an API_key that would be used in the scripted. After i input the API_key into the script and run it i attempt a failed remote desktop attempt from my host computer and everything work as expected.
• After seeing that script is working i went back into the log analytics work space i went to create a custom log then i had to copy the log file that is outputted by the previous script and paste it to a notepad file on my host computer and upload that file to the custom log. Then I selected the host type windows and file path, and created the log. Next i went to extract and parse the raw data in the custom logs. I highlighted the values and named the sections of data that i wanted to create, which are Longitude, Latitude, Username, Sourcehost, State, Country, Time stamp. My honeypot had not been discovered yet so i went and attempted another failed logon to see if my custom log parsing is working correctly and it was.
• Next i went back to the sentinel platform and went to work books to add a new one. Then i edited the work book and added a query to search the data from the custom log and set the visual to map out the geolocation on a world map by either country or Longitude/Latitude
• The final task was to wait several hours and came back. I found that several attempt had been made to bruteforce into the honeypot and recorded the data.

Active Directory and Group Policy

• The first thing that I did in this lab is open oracle virtual box and created my first virtual machine which was a Windows 2019 server that I name DC and planned to make the Domain Controller. While creating the virtual machine I made sure to add a second network adapter in the oracle settings. The First one being connected to my home internet and the second for the internal network that the client machines would connect to.
• Now after starting the VM and setting up my Administrator account with a password I went to look at the two network adapters that I created now with in the GUI and checked the statuses to determine which belong to the internal network. Because of its APIPA IP address i was able to find the adapter, went to the properties configured a manual network address and subnet mask, and used the loop back address for the DNS server setting.
• Then I went to server manager and to add roles and features and began to install Active Directory domain services. Then I did the post configuration and made the server officially a Domain controller and named a new forest before installing and rebooting the server.
• After the restart logged in and went to create a domain administrator account that would be used to do day to day task. I went to Active Directory Users and Computers created and organizational unit for Admins and added a user there. Then went to the new users properties, added the Domain Admin group and then signed into the new administrator.
• Once signed in I went to add roles and features to add the remote access feature to allow my client machines to be able to access the internet through Network Address Translation while in the domain. Then went to tools selected routing and remote access so I could configure NAT on my external interface.
• After this the next step was to and add DHCP services so that my client machines can receive IP addresses upon entering the domain. Then went to tools to configure my DCHP and define the scope of addresses that would be used.
• Before adding my client machines I used a PowerShell script to add new users that I can later use in the lab environment
• After going to virtual box and creating the new VM I just made sure the network adapter was connected to the internal network that the Domain Controller was in. Once the windows client machine was started I immediately check to see if DHCP was working correctly on the command line with ipconfig, then in advanced system settings I went and join the Domain I created.
• Finally after the restart of my client machine the final test was to log into one of the many accounts I created on the domain.