My Services

Implementing SSL/TLS certificates. Knowledge of security practices like firewalls, VPN and Remote Desktop Connection.

Best practices for Windows Firewall with Advanced Security
IF attackers can scan for and discover open instance ports, such as port 3389 on a Windows instance and port 22 on a Linux instance, they can initiate attacks on these ports. You can prevent the attacks by modifying the default port or restricting access sources. In this topic, an instance that runs Windows Server is used to describe how to use Windows Firewall with Advanced Security (WFAS) to restrict access from specific IP addresses.
Use MMC to configure Windows Firewall

1. Enable the firewall
. Press the shortcut keys Win+R to open the Run dialog box.
1) Enter firewall.cpl and press the Enter key.
2) Click Turn Windows Firewall on or off to view the firewall status.
2. Check Remote Desktop Protocol (RDP) port 3389.
. Press the shortcut keys Win+R to open the Run dialog box.
1) Enter wf.msc and press the Enter key.
2) Click Inbound Rules. Sort by column Local Port to see if any 3389 rule is enabled.
3. Add RDP port 3389 to Windows Firewall with Advanced Security.
.In the Actions section, Click New Rule.... The New Inbound Rule Wizard dialog box appears.
1) In the Rule Type step, select Port and click Next.
2) In the Protocol and Ports step, select TCP as the protocol, select Specific local ports and enter 3389 in the field, and then Click Next.
3) Select Allow the connection and click Next.
4) Use the default settings and click Next.
5) Enter a rule name. In this example, RemoteDesktop is used. Click Finish.
4. Configure the scope.
. Right-click the created RemoteDesktop inbound rule and click Properties
1) On the Scope tab, select These IP addresses: in the Remote IP address section, add one or more IP addresses or CIDR blocks, and then click OK.
Notice After the parameters on the Scope tab are configured, only IP addresses that you have specified in the Remote IP address section can access to the Windows instance
5. Add an IP address to the Remote IP address section. | In this example, 192.168.144.10 is added. Then, click OK.

If you enter the below syntax it will redirect http to https using .htaccess
RewriteEngine On
RewriteBase /
RewriteCond %{HTTP_HOST} ^perpetualcalendar.epizy.com [NC]
RewriteRule ^(.*)$ https://www.perpetualcalendar.epizy.com/$1 [L,R=301]
save the text file as .htaccess

Lets check it now...
if you enter the below syntax it will redirect domain1.com to domain2.com using .htaccess
RewriteEngine On
RewriteBase /
RewriteCond %{HTTP_HOST} ^www.perpetualcalendar.epizy.com [NC]
RewriteRule ^(.*)$ https://www.projectmini.kesug.com/$1 [L,R=301]

Lets check it now...

That's it.

PowerShell code for pinging and logging results

This approach allows you to ping multiple targets and store the results in a more structured format (txt), suitable for further analysis.

$computers = "172.15.0.1", "172.15.0.2", "www.google.com" # Example: add more IP addresses or hostnames
$results = foreach ($computer in $computers) {
$ping = Test-Connection -ComputerName $computer -Count 1 -Quiet
[PSCustomObject]@{
ComputerName = $computer
Online = $ping
ResponseTime = if ($ping) {
(Test-Connection -ComputerName $computer -Count 1).ResponseTime
} else { "N/A" }
}
}
$results | Format-Table -AutoSize
# Log to a File
$results | Format-Table -AutoSize | Out-File "C:\Users\user\Desktop\PingLog.txt"

How to password protect your site

The following steps create an .htpasswd and .htaccess file to protect either an entire website, a specific subdirectory, or specific files.

Create the .htpasswd file
Log into your server via SSH.
Navigate into the directory you wish to password protect.
This would either be example.com for your entire website or example.com/subdir for a subdirectory.

Run pwd to confirm the full file path to this directory. Make a note of this.
pwd
/home/username/example.com
Create an .htpasswd file by running the following command.
Change the directory path and user1 to the name of the login user you wish to create.

htpasswd -c /home/username/example.com/.htpasswd user1
When prompted, enter a password for the new user. The code in your .htpasswd file then displays the encrypted password like this:
user1:$apr1$bkS4zPQl$SyGLA9oP75L5uM5GHpe9A2
Run the command again (without the -c option) for any other users you wish to allow access to your directory.

Set the permissions to 644.
chmod 644 .htpasswd

This example password protects an entire website or subdirectory, depending on the file path.

#Protect Directory
AuthName "Dialog prompt"
AuthType Basic
AuthUserFile /home/username/example.com/.htpasswd
Require valid-user

Protect a single file
This example password protects a single file named admin.php:

#Protect single file

AuthName "Dialog prompt"
AuthType Basic
AuthUserFile /home/username/example.com/.htpasswd
Require valid-user
This example protects multiple files such as admin.php and staff.php.

#Protect multiple files

AuthName "Dialog prompt"
AuthType Basic
AuthUserFile /home/username/example.com/.htpasswd
Require valid-user

Protect a WordPress subdirectory

Due to how WordPress routes all page requests, attempting to access a password protected subdirectory will throw a 404 Not Found error. To resolve this, you must an extra line to the .htaccess file to reference ErrorDocument.
This example protects a subdirectory named members.

ErrorDocument 401 default

#Protect Directory
AuthName "Dialog prompt"
AuthType Basic
AuthUserFile /home/username/example.com/members/.htpasswd
Require valid-user

Test your site
Visit your website and test if your new password prompt is displaying as configured.