<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Adeoye Iyanuoluwa David on Medium]]></title>
        <description><![CDATA[Stories by Adeoye Iyanuoluwa David on Medium]]></description>
        <link>https://medium.com/@adeoyedavid55?source=rss-935cded74d48------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*uHeANqmGHOg1C5j_tb-SMQ.jpeg</url>
            <title>Stories by Adeoye Iyanuoluwa David on Medium</title>
            <link>https://medium.com/@adeoyedavid55?source=rss-935cded74d48------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 17:27:58 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@adeoyedavid55/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[SECURITY CONTROLS (DIRECTIVE CONTROL)]]></title>
            <link>https://medium.com/@adeoyedavid55/security-controls-directive-control-994891744f03?source=rss-935cded74d48------2</link>
            <guid isPermaLink="false">https://medium.com/p/994891744f03</guid>
            <dc:creator><![CDATA[Adeoye Iyanuoluwa David]]></dc:creator>
            <pubDate>Mon, 28 Jul 2025 18:30:18 GMT</pubDate>
            <atom:updated>2025-07-28T18:30:18.728Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*SKc5KriXY1neoGPmGMujSA.jpeg" /></figure><p>Directive controls are designed to influence or guide user behavior by providing clear instructions or warnings before an action is taken. In this lab, I implemented a <strong>directive control</strong> by configuring a <strong>login warning banner</strong> that displays a security message to users during the sign-in process. The objective of this control is to remind users of their responsibilities, legal obligations, and acceptable use policies when accessing the system.</p><p>This control provides instruction to direct a user towards more compliant behavior. In this lab I configured a directive control in the form of a login warning banner. Finally, I test the directive control.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3oRuOQxmhqQZOQKJzL2QJQ.png" /><figcaption>Opened ‘PowerShell (Admin)’ &gt; entered the warning banner as a code.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0pl01EdKhelz_o9MpU85Nw.png" /><figcaption>The Directive control is now being displayed as a warning banner.</figcaption></figure><h4>CONCLUSION</h4><p>The lab successfully demonstrated the application of a directive control through the use of a login warning banner. By executing the appropriate PowerShell command as an administrator, I was able to configure a message that now appears before login. Upon testing, the warning banner was clearly displayed, serving as an effective deterrent against unauthorized use and reinforcing the organization’s security policies. This control plays a vital role in promoting user awareness and fostering a culture of compliance and accountability.</p><h4>DISCLAIMER</h4><p>This lab was conducted in a test environment for educational and demonstration purposes only. Warning banners should be carefully crafted to align with your organization’s legal, compliance, and security standards. Before implementing directive controls in a production environment, consult your organization’s legal or compliance team to ensure the language and placement of such warnings meet regulatory and policy requirements.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=994891744f03" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[SECURITY CONTROLS (DETECTIVE CONTROL)]]></title>
            <link>https://medium.com/@adeoyedavid55/security-controls-detective-control-ad0e714fa636?source=rss-935cded74d48------2</link>
            <guid isPermaLink="false">https://medium.com/p/ad0e714fa636</guid>
            <dc:creator><![CDATA[Adeoye Iyanuoluwa David]]></dc:creator>
            <pubDate>Mon, 28 Jul 2025 18:25:59 GMT</pubDate>
            <atom:updated>2025-07-28T18:25:59.094Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*ELYAb_MUzPb8PPTgXfrnVw.jpeg" /></figure><p>This control records log each time an event occurs, regardless of if the event is benign or malicious.</p><p>For this activity, i first perform an activity that will not be logged. Then i configured the logging to record that activity and then i performed the activity again.</p><p>Finally, i reviewed the log to confirm the record of the activity was created.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6TkLk-aSiTbcHCJNOBB7Mg.png" /><figcaption>Opened the folder created for this activity ‘LABFILES’ &gt; I deleted a file in the folder</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y9KibBn6vVX-IDgBpJ5ntg.png" /><figcaption>Opened Event Viewer</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F96R5BP8OK7mzPjS9O8ZXg.png" /><figcaption>Opened Windows Logs</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AA3PQnORFbrG1lDW4s2cNg.png" /><figcaption>Selected Security (to open and display security logs)</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tRioBwjPCC5G0CBvd_HiBA.png" /><figcaption>Select ‘Find’ in the find field i typed the name of the deleted file &gt; Find Next</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6r56Layw-fnAqYMmoLueuQ.png" /><figcaption>Event Viewer came back with no result</figcaption></figure><h4>CONFIGURE EVENT LOGGING</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KCWT33wWSMs7SP35d_KZFQ.png" /><figcaption>Search Local Security Policy</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IuzJX_vEbrK1r7jxKrpbGg.png" /><figcaption>Select Audit Policy (under Local Policies)</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5uEbSxn8nDmPvcfNsJ6XrQ.png" /><figcaption>Right click ‘Audit Object Access’ and then select ‘Properties’ &gt;Thick ‘Success &amp; Failure’</figcaption></figure><p><strong>NOTE:</strong> While the main switch for auditing object access activities is now on, auditing will not occur on most file objects until an on-object auditing setting is made.</p><p>Went back to the folder ‘LABFILES’ and select Properties</p><p><strong>Select</strong> ‘Security’ and then ‘advanced’</p><p><strong>Select</strong> ‘auditing’</p><p><strong>Select</strong> ‘Continue’</p><p><strong>Select</strong> ‘Add’</p><p><strong>Select</strong> ‘Select a principle</p><p><strong>Type</strong> ‘Everyone’ and then select ‘Check Names’ select ‘Ok’</p><p><strong>Select</strong> ‘Show advanced permissions’</p><p><strong>Select</strong> to mark ‘Delete subfolders and files’ and ‘Delete’ checkboxes select ‘Ok’</p><p><strong>Select</strong> to mark ‘Replace all child object auditing’ checkbox select ‘Ok’ to save</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6TkLk-aSiTbcHCJNOBB7Mg.png" /><figcaption>Delete another file ‘pcaps’</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j1EzsapZ0lXEEzNABz9dyw.png" /><figcaption>Type/search ‘4660’ (4660 is the Event ID for the event type of object deletion) &gt; select ‘cancel’</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*57peUMKubcu8Z8k3MRQDRw.png" /><figcaption>Event ID: 4660</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xBodMnMAuGNpfKYmeLle1Q.png" /><figcaption>Details of the Event.</figcaption></figure><h4><strong>CONCLUSION</strong></h4><p>This lab successfully demonstrated the implementation of a <strong>detective control</strong> using Windows audit logging to monitor file deletion activities. Initially, a file was deleted from the ‘LABFILES’ directory without any corresponding log entry, indicating that auditing was not enabled. After configuring the <strong>Audit Object Access policy</strong> and applying auditing settings directly to the folder, I repeated the deletion activity. This time, the deletion was captured and recorded in the <strong>Security event log</strong> under <strong>Event ID 4660</strong>, confirming that the detective control was functioning as intended. This process highlights the importance of enabling both system-wide auditing and object-level audit entries to ensure comprehensive visibility into critical file access and deletion events — key for compliance, forensic investigation, and overall security posture.</p><h4>DISCLAIMER</h4><p>This activity was carried out in a controlled lab environment strictly for training and demonstration purposes. The configuration and testing of audit policies should always be performed with caution and in accordance with your organization’s IT governance, data protection policies, and security standards. In production environments, enabling object access auditing can generate a high volume of logs and may require appropriate storage and log management planning.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ad0e714fa636" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[SECURITY CONTROLS (PREVENTIVE CONTROLS)]]></title>
            <link>https://medium.com/@adeoyedavid55/security-controls-preventive-controls-74be7d056034?source=rss-935cded74d48------2</link>
            <guid isPermaLink="false">https://medium.com/p/74be7d056034</guid>
            <dc:creator><![CDATA[Adeoye Iyanuoluwa David]]></dc:creator>
            <pubDate>Mon, 28 Jul 2025 18:19:56 GMT</pubDate>
            <atom:updated>2025-07-28T18:19:56.331Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LHQMwI4nYDlz99MtmkPl4w.jpeg" /></figure><p>As a Security Expert, you are always working to improve the organization’s stance. Configuring, using and testing security controls is a daily task to ensure you understand the nature of the various security controls your organisation might be needing .</p><p>It is important to facilitate recommendations on effective remediations to resolve security weaknesses.</p><h3>PREVENTIVE CONTROLS</h3><p>Preventive controls attempts to stop unwanted, malicious activity from taking place.</p><p>In this lab I first performed an undesirable activity, after which I then implement a preventive control to block the activity. Finally, I attempt the activity again to test the preventive control.</p><p>I configured a folder ‘TOOLS’ (the folder hold utilities and data files that must only be accessible to domain and local administrators only. Users without administrative rule should not be able to use view, hence they are prevented from viewing the share.</p><h4>VERIFY PERMISSION</h4><p>Verify if the share has been configured with appropriate permissions by trying to access it using a non-administrative account.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cqYlNC4oK_vTrxykX_GvZg.png" /><figcaption>File share is accessible, hence no preventive control in place.</figcaption></figure><p>(Account accessing it isn’t an administrative account and should not have access. Now I need to implement a preventive control so that non-administrative account cannot access this share)</p><h4>Moving back to the server where the Folder is saved</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qErSdbR20pswRG-qaNgayw.png" /><figcaption>Server Manager &gt; File &amp; Storage Service &gt; Shares</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mWXCzuhjN8SbTtsQTU2bPQ.png" /><figcaption>Right click on tools &gt; properties to get the options &gt; then click permissions &gt; Customize Permissions</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rg9PpzD2QWMkVqdioeMD2A.png" /><figcaption>Clicked on Disabled Inheritance</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ffyqIWIdnTofKUeg-mGVUg.png" /><figcaption>Disabling Inheritance</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*20T0Y0FmAgUy3YPC74EyQg.png" /><figcaption>Removed the two ‘Users’ under Principals &gt; Saved the changes</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*enkMhCUTbfJhmkckdvO9XQ.png" /><figcaption>Went back to the Non-administrative account and access to the folder is no longer granted</figcaption></figure><h3>CONCLUSION</h3><p>In this lab, I demonstrated the configuration and validation of a <strong>preventive control</strong> to restrict unauthorized access to a sensitive file share. Initially, a non-administrative user was able to access the ‘TOOLS’ folder, indicating a lack of proper access restrictions. By disabling inheritance and removing the default user permissions, I enforced a security control that ensures only domain and local administrators can access the folder. Re-testing confirmed that the non-administrative account no longer had access, effectively validating the preventive control. This exercise reinforces the importance of regularly reviewing and adjusting permissions to maintain least-privilege access and protect critical assets from unauthorized access.</p><h3>DISCLAIMER</h3><p>This lab was conducted in a controlled test environment for educational and demonstration purposes only. No live production systems were affected. All actions taken comply with organizational policies and security guidelines. Ensure all security controls are implemented in accordance with your organization’s governance, compliance requirements, and change management procedures before applying them in a production environment.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=74be7d056034" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[SYSTEM HARDENING (DEVICE AND DRIVER MANAGEMENT)]]></title>
            <link>https://medium.com/@adeoyedavid55/system-hardening-device-and-driver-management-ecfae6beae62?source=rss-935cded74d48------2</link>
            <guid isPermaLink="false">https://medium.com/p/ecfae6beae62</guid>
            <dc:creator><![CDATA[Adeoye Iyanuoluwa David]]></dc:creator>
            <pubDate>Wed, 16 Jul 2025 17:50:27 GMT</pubDate>
            <atom:updated>2025-07-16T17:54:35.091Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1002/1*FdEkt-Z0S5UyDzG9KQJsOQ.jpeg" /></figure><p>When evaluating a system to improve the security and achieve system hardening, one of the important steps is to discover that there are some device drivers that are present on the systems. Knowing how to remove these devices and their drivers is important to system hardening.</p><p>I will scan for changes, update driver, disable and re-enable device, remove a device driver and install a device driver.</p><p>The concept of system hardening is focused mainly on Remove and Update. On the one hand it is important to remove anything not needed for business activity and on the other hand, anything identified to be needed needs to be secured and updated.</p><p>It should be noted that the process of hardening is more complex than it might appear to be. This is because it’s not always the easy remove and update, sometimes you might have to update, then remove, then update again and remove again, it might take several repeated steps to achieve a proper hardening.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/645/1*nJrG6UqB_rZENiavNz6_mA.png" /><figcaption>Opening Device Manager, scan for hardware changes</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/817/1*jwv-ttRkKTM7XJtkkKzsVw.png" /><figcaption>After scanning, Microsoft Virtual DVD-ROM is being updated</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/831/1*h_-R9Nnr0nvOZ0zBBwxyFw.png" /><figcaption>Update completed</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/819/1*pYOfuXcDVZ-7ukYpIIQ2sg.png" /><figcaption>After the update, the DVD-ROM will then be disabled and enabled again,</figcaption></figure><p>(Disabling and Enabling is considerd a troubleshooting step and used to see if this process will make any device to start working properly)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/830/1*i4ulZRtn7Xd_K-osChzvbg.png" /><figcaption>The DVD-ROM should be Uninstalled</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/830/1*FcOwKJZUFrPIiNktmk13Vw.png" /><figcaption>After uninstalling the DVD-ROM is no longer in the Device Manager</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/663/1*UYH46WOqd_7JsQjlqfak2Q.png" /><figcaption>If a Scan for hardware changes is done, then the DVD-ROM appears again, these devices were discovered and installed again after the scan.</figcaption></figure><h3><strong>REMOVING UNNEEDED APPLICATIONS AND SERVICES</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/756/1*lC2F06z101hRHM78EAsL5w.png" /><figcaption>I have an unneeded application ‘CPUID’ that needs to be uninstalled</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/821/1*mMtgsM4Z33gJcC-Q6wH1Gg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/830/1*AVdNDrYdPYe3jXe0G9aN5A.png" /><figcaption>CPUID being uninstalled.</figcaption></figure><h3>USE REMOVE ROLES AND FEATURES TO REMOVE THE FTP SERVICE</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/831/1*4y4Cc_S1dIS_bt4vVWnYMg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/830/1*zme7hTHGUsejO0tQGkkzSw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/816/1*3CUxMdozg2KNKWqgHzE3cQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/830/1*TtWpsecQR7R3DtileutVog.png" /><figcaption>In Server roles, Web Server (IIS) was expanded and FTP Server was unchecked.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/830/1*W6XFaS7V5fVCJTRYLzXjtg.png" /><figcaption>Restart the destination server automatically if required needs to be checked.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/794/1*kwPQmyjzycFxO9Nl15eGyA.png" /><figcaption>YES was selected.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/821/1*0W403as-ElvwqebbeJgSEw.png" /><figcaption>Once removal is complete, the system will reboot.</figcaption></figure><h3><strong>MANIPULATE HOSTS FILE NAME RESOLUTION</strong></h3><p>Dynamic DNS is key to modern networks, there are instances where we need to manipulate the local hosts file-based name resolution is necessary.</p><p>System hardening includes forcing specific resolution or blocking a resolution to prevent compromise or vulnerability exploitation.</p><p>I will be manipulating a hosts file to force the resolution of a FQDN to a specific IP address, I will prevent the resolution of a specific FQDN and will remove a false FQDN to IP mapping.</p><h4>USE wget TO VISIT JUICESHOP.LOCAL</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/798/1*7Am9LP3Qp_jdN16IEv3nYA.png" /><figcaption>Wget juiceshop.local</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/799/1*tmQA0dBPCzmFswAhNqch-Q.png" /><figcaption>IPv4 address the domain resoves to 203.0.113.228, index.html is saved.</figcaption></figure><h3>VIEW THE CONTENTS OF THE CURRENT /etc/hosts file</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/817/1*yjhowj7jc2NwLU5Ltn2i9g.png" /><figcaption>Cat /etc/hosts to get the content of the current hosts file (Juiceshop.local- 203.0.113.228)</figcaption></figure><h3>INTRODUCE A NAME RESOLUTION ERROR BY EDITING THE /etc/hosts file USING NANO</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/783/1*wKBavl8b7_OfWB0rXjjubg.png" /><figcaption>Juiceshop.local changed to 203.0.113.249</figcaption></figure><h3>USE wget TO VISIT juiceshop.local</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*hq8-fsPiMw_GNuXQ6OeTUg.png" /><figcaption>Juiceshop.local domain now resolves to 203.0.113.249</figcaption></figure><p>Wget will wait for a connection that will surely never be established.</p><p>This shows that a fake entry in a local hosts file will prevent access to a real site because the content of the hosts file will always take precedence over a DNS query. This is a means to block access to a FQDN.</p><h3>ALTER juiceshop.local BACK TO THE CORRECT DOMAIN.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/790/1*JACZaEUXxv2zYd4bjkxo3A.png" /><figcaption>After this wget juiceshop.local now resolves to the right domain.</figcaption></figure><p><strong>Disclaimer</strong><br>The names, organizations, and scenarios presented in this report are entirely fictional and are used solely for illustrative and educational purposes. They do not represent any real individuals or companies. Any resemblance to actual persons, living or dead, or actual entities, past or present, is purely coincidental.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ecfae6beae62" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[HARDENING SYSTEM BY SETTING FIREWALL]]></title>
            <link>https://medium.com/@adeoyedavid55/hardening-system-by-setting-firewall-c11dc9bfc2aa?source=rss-935cded74d48------2</link>
            <guid isPermaLink="false">https://medium.com/p/c11dc9bfc2aa</guid>
            <dc:creator><![CDATA[Adeoye Iyanuoluwa David]]></dc:creator>
            <pubDate>Wed, 16 Jul 2025 17:42:41 GMT</pubDate>
            <atom:updated>2025-07-16T17:42:41.082Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DgNvKc5A9wI-ED0P7afpDw.jpeg" /></figure><h3>BLOCKING INBOUND COMMUNICATIONS</h3><p>Hardening is an important aspect of security, as a cybersecurity analyst one of your important task is to reduce the attack surface of your organisation and this include system hardening and setting firewall rules to block certain communications to your organisation network.</p><p>I’ll be walking us through how I was able to perform system hardening by blocking ICMP Communications through setting firewall rules. This was for me to modify enterprise capabilities to enhance security.</p><p>One of the challenges we had was that our server still responded to ICMP Communications, and I was tasked with the responsibility of applying chnages to the server firewall to ensure future ICMP Communications were blocked.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/685/1*GQJLgFypyNAk8-9GRrzSQg.png" /></figure><p>From the image above it can be seen that the server DC10 can be triggered for an ICMP response, which means the server is not in compliance with system hardening requirement.</p><h4>SET INBOUND RULES</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/724/1*QzD9Z5NgRDMISKkrINtAMA.png" /><figcaption>On the Server I opened <strong>‘Windows Defender Firewall’</strong> were the rules would be set.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/798/1*DWyKnFWDHOZ2Z0SoDo-xnA.png" /><figcaption>Opened up Advanced Settings</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/707/1*2-5fd8PmEgbt3-Q03U9xRA.png" /><figcaption>Opened up Inbound Rules</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/757/1*N4gKz5Sz3g3f-LVVze0hqg.png" /><figcaption>Opened up File and Printer Sharing (Echo Request — ICMPv4 / ICMPv6-In)</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/723/1*CmhQ2tMEDsScLj8V_8Jl8Q.png" /><figcaption>Went on to the properties</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/726/1*-dXcP6PT59N5_97V3IYveA.png" /><figcaption>Blocked the connection</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/749/1*8kgbQPrKa2FuPLHY7VSnlA.png" /><figcaption>Trying to Ping the Server again and now getting ‘Request Timed Out’</figcaption></figure><p>This indicates that ICMP Communications were unsuccessful, because the firewall settings now block inbound ICMP requests.</p><h3><strong>HARDENING SYSTEM BY SETTING FIREWALL RULES (To manage shared folder access)</strong></h3><p>Managing file share is another form of system hardening.</p><p>In the organisation it is common for files to be easily shared and access, however hardening now requires that this be managed over firewall rules. Firewall rules need to be configured to block access to file shares.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/659/1*6sIgE46MkmyNPSJL-tgp7w.png" /><figcaption>Test files has been created to be shared</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/661/1*b_KtDawzuid0ugORoxQgbA.png" /><figcaption>Folder being configured to be shared</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/673/1*Ctq63-L4t6CXUirdq3b4zQ.png" /><figcaption>Attempting to access the shared file</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/657/1*W78wBzQU5cXzL6OStPC4lA.png" /><figcaption>Shared folder easily accessible. Shows that access to share from client system is currently possible.</figcaption></figure><p>Now we need to configure firewall to block any access to shares from client system.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/677/1*inPqHTGa1zbGtGE-rgHMrw.png" /><figcaption>Open windows defender firewall</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/715/1*PfWK7oh5D72x2ZKACEEjfA.png" /><figcaption>Open advance settings.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/686/1*XPjypic1HPraO4b0xzMH2A.png" /><figcaption>Opened Inbound Rules and locate File and Printer Sharing (SMB-In)</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/696/1*KNg1GGegvKwZcPJ-FnWG4A.png" /><figcaption>Opened up the Properties</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/790/1*4Lw47CsANJFzdHru3VCpyA.png" /><figcaption>Here I blocked the connection.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/668/1*j8OBV6mWm1x-fdCNZbUcow.png" /><figcaption>In General I checked Enabled…And block the connection</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/691/1*cuaxS33-S912E30tCL-vUQ.png" /><figcaption>After configuring the Firewall….I tried to access the shared folder and got a ‘Network Error’</figcaption></figure><p>This shows that the attempt to access the shared files failed. This is because the current settings of the Windows Defender Firewall do not allow file and Printer sharing across network.</p><h3>NOTE:</h3><p>If a Firewall rule is disabled, but the associated communication is still able to occur, this might be due to the fact that one or more other rules are allowing the communication.</p><p><strong>Disclaimer</strong><br>The names, organizations, and scenarios presented in this report are entirely fictional and are used solely for illustrative and educational purposes. They do not represent any real individuals or companies. Any resemblance to actual persons, living or dead, or actual entities, past or present, is purely coincidental.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c11dc9bfc2aa" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[INFORMATION SECURITY MANAGEMENT SYSTEMS (ISMS)]]></title>
            <link>https://medium.com/@adeoyedavid55/information-security-management-systems-isms-bc18ada3ebab?source=rss-935cded74d48------2</link>
            <guid isPermaLink="false">https://medium.com/p/bc18ada3ebab</guid>
            <dc:creator><![CDATA[Adeoye Iyanuoluwa David]]></dc:creator>
            <pubDate>Fri, 11 Jul 2025 17:54:34 GMT</pubDate>
            <atom:updated>2025-07-11T17:54:34.764Z</atom:updated>
            <content:encoded><![CDATA[<p>In today’s rapidly evolving digital landscape, robust cybersecurity practices are not a luxury they are a necessity. As organizations become increasingly reliant on digital infrastructures and cloud-based services, the threats to information integrity, confidentiality, and availability grow in both complexity and scale. To stay ahead of these threats, Chester Business Ltd (CBL) has implemented a comprehensive <strong>Information Security Management System (ISMS)</strong> in alignment with <strong>ISO/IEC 27001:2022 standards</strong>.</p><p>This blog post explores how CBL leverages <strong>threat modelling</strong>, particularly through advanced tools like <strong>IriusRisk</strong>, to proactively identify, assess, and mitigate risks within its information systems. It outlines our approach to integrating threat intelligence into the system development lifecycle and describes the methodology, objectives, and real-world threat landscape CBL addresses. Moreover, it examines the broader context of ISMS implementation covering leadership, planning, operational controls, performance evaluation, and continuous improvement.</p><p>Through a blend of structured policies, strategic leadership, and data-driven decision-making, this article provides an in-depth look at how CBL is fortifying its digital ecosystem and building a culture of security that aligns with regulatory demands, stakeholder expectations, and industry best practices.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GREYmBUp41u8vpVlO79QjQ.png" /></figure><h3><strong>THREAT MODELING</strong></h3><p><strong>INTRODUCTION:</strong></p><p>Threat modelling is a fundamental component of cybersecurity, particularly in the realm of designing secure systems. Threat modelling is indeed a crucial practice for identifying and evaluating potential risks to an organization’s information systems. Leveraging advanced tools like Iris Risk, and Chester Business Limited (CBL) can enhance the efficiency and effectiveness of its threat modelling processes. Iris Risk provides a comprehensive platform for analysing and managing security risks, allowing CBL to systematically assess its systems’ architecture, data flows, and potential attack vectors. By integrating Iris Risk into the development lifecycle, CBL can streamline the threat modelling process, identify potential threats more accurately, and prioritize mitigation efforts effectively. This proactive approach to security empowers CBL to stay ahead of emerging threats, strengthen its security posture, and safeguard its systems against potential attacks. Through the strategic utilization of Iris Risk, CBL ensures that security remains a top priority throughout the system’s design and implementation phases.</p><h4><strong>OBJECTIVES</strong></h4><p>At CBL, the objectives of conducting threat modelling with Iris Risk are multi-faceted and strategic. At CBL, the objectives of conducting threat modelling with Iris Risk are multi-faceted and strategic. Primarily, the organization aims to meticulously identify potential security threats and vulnerabilities within its systems and applications, ensuring a comprehensive understanding of its risk landscape. Subsequently, CBL seeks to assess these risks, by evaluating their likelihood and potential impact to prioritize mitigation efforts effectively. By bolstering existing security controls and integrating additional safeguards, CBL endeavours to enhance its security posture and fortify its defences against potential attacks. Compliance with regulatory requirements and industry standards is paramount, and CBL conducts thorough threat modelling exercises to demonstrate due diligence and mitigate legal and financial liabilities. Furthermore, CBL views threat modelling as an iterative process, continuously revisiting and refining its threat models to adapt to evolving threats and changes in the organizational landscape, thus ensuring the ongoing improvement of its security posture and resilience against emerging risks. The completed threat modelling process thoroughly analyses, evaluates, and suggests strategies for mitigating these risks, seamlessly incorporating them into system upgrades to detect emerging threats effectively. Through these objectives, CBL endeavours to safeguard its sensitive information and assets, maintain the trust of its stakeholders and uphold its commitment to excellence in cybersecurity.</p><h4><strong>METHODOLOGY</strong></h4><p>At CBL, threat modelling with Iris Risk follows a meticulous process, starting with scope definition and asset identification. Collaborative efforts and threat intelligence sources are leveraged to enumerate potential threats and vulnerabilities. Vulnerability analysis pinpoints weaknesses, followed by risk assessment for prioritization. Mitigation planning tailors approaches to address risks, integrating security into development. Continuous improvement includes regular model updates and documentation for transparency. Asset identification is facilitated through maintaining an accessible asset repository. Figure (1): Data Flow Network Diagram of CBL Network’s architecture. Figure (2): Diagram of CBL Network’s architecture generated using the threat modelling tool IRIUS Risk</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/903/1*ejc_Z3oM3CXSuSnDPjYYMw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/903/1*V9TFF3wtlUWXNATBLBV4zw.png" /></figure><h3><strong>THREAT DISTRIBUTION</strong></h3><p>The threat model for Chester Business Limited provides a detailed analysis of potential risks, A total of <strong>85 threats</strong> categorizing them into critical threats<strong> (37.65%)</strong>, high threats <strong>(56.47%)</strong>, and medium threats <strong>(5.88%)</strong>. This breakdown highlights the wide spectrum of risks encountered by Chester Business Ltd. For visual representation, please refer to the accompanying figure, which also depicts the number of threats within each risk rating level across four categories.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/861/1*uV_8VNCDREXxalyTRwMNFw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/573/1*awykCw-5gbj5AaJqHIugtw.png" /></figure><p>Based on the information provided, the current threat risk is at 68.05%, which is categorized as “Medium”. This indicates that there is a significant level of security risk. Out of the 85 identified threats, 48 of them are classified as “High”, and 32 are categorized as “Critical”. This means that almost half of the threats are of high concern, and a significant portion of them are critical. Overall, the security status appears to be concerning, with a substantial number of high-risk threats and a high projected risk.</p><h4><strong>Unveiling Threats</strong></h4><p>In cybersecurity, the threat model acts as our guiding light, revealing the dangers ahead. Critical threats make up 35.19%, including APTs and Zero-Day Exploits. High risks, at 40.74%, involve DDoS attacks and Data Breaches. Medium risks, at 7.41%, include Phishing Attacks. This report isn’t just numbers; it’s a call to action, urging swift response and fortification.</p><h3><strong>FORTIFYING OUR DEFENCES: COMPREHENSIVE MITIGATION STRATEGIES</strong></h3><p>Here’s a holistic set of mitigation strategies, addressing both critical and high-risk threats identified in the report, and incorporating essential cybersecurity practices.</p><h4><strong>Mitigating Critical Threats</strong></h4><p><strong>Ø Défense in Depth Approach:</strong> Establish a multi-layered Défense strategy, incorporating network segmentation, robust access controls, and encryption protocols. This approach, outlined in standards like NIST Special Publication 800–53, forms a formidable barrier against sophisticated threats.</p><p><strong>Ø Continuous Monitoring and Incident Response:</strong> Deploy advanced threat detection mechanisms complemented by a well-defined incident response plan. Real-time monitoring, coupled with automated incident response systems, as advocated by SANS Institute, enables swift mitigation of critical threats.</p><p><strong>Ø User Education and Training:</strong> Foster a culture of cybersecurity awareness through regular training sessions and simulated phishing exercises. Empower employees to recognize and report suspicious activities, mitigating the risk of insider threats.</p><p><strong>Ø Patch Management and Regular Updates:</strong> Institute rigorous patch management practices, ensuring timely updates of software and systems to address known vulnerabilities. Regularly updating and patching systems is a fundamental defense against exploit-based attacks.</p><h4><strong>Mitigating High Risks</strong></h4><p><strong>Ø Strengthening Network Defenses:</strong> Bolster perimeter defenses with next-generation firewalls, intrusion detection and prevention systems, and robust access controls. Implement DDoS protection mechanisms, as recommended by industry leaders like Cisco, to defend against network-based threats.</p><p><strong>Ø Endpoint Security Measures:</strong> Deploy comprehensive endpoint protection solutions encompassing antivirus software, endpoint detection and response (EDR) tools, and device encryption. These measures safeguard against malware infections and unauthorized access to sensitive data.</p><p><strong>Ø Data Protection and Privacy Controls:</strong> Enforce stringent data protection measures, including encryption, access controls, and data loss prevention (DLP) tools. Comply with relevant privacy regulations such as GDPR (<em>EU General Data Protection Regulation (GDPR) — an Implementation and Compliance Guide, Fourth Edition</em>, 2020) or CCPA, bolstering resilience against data breaches.</p><h4><strong>General Cybersecurity Practices</strong></h4><p><strong>Ø Incident Response Planning:</strong> Develop and regularly update incident response plans to streamline responses to security incidents. Clearly delineate roles and responsibilities, ensuring a coordinated and effective response in the event of a breach.</p><p><strong>Ø Cyber Education and Routine Practices:</strong> Promote cyber education initiatives at all levels of the organization, emphasizing the importance of cybersecurity best practices. Encourage routine cybersecurity hygiene practices, such as strong password management, software updates, and data backup procedures.</p><p><strong>Ø Resilience Measures:</strong> Implement resilience measures such as data backups, disaster recovery plans, and business continuity strategies. Prepare for contingencies to minimize downtime and mitigate the impact of security incidents on business operations.</p><p>By embracing these comprehensive mitigation strategies, CBL can fortify its defences against an ever-evolving threat landscape. Remember, cybersecurity is not merely a task to be completed but an ongoing journey of vigilance and adaptation.</p><h4><strong>ISMS BUSINESS CONTEXT OF CBL</strong></h4><h3><strong>CLAUSE 4: CONTEXT OF THE ORGANIZATION</strong></h3><p>As the CIO of Chester Business Ltd (CBL), assessing the context of the organization involves understanding the internal and external factors, stakeholder requirements, and scope of the ISMS and implementing ISMS in line with ISO27001 standards, that could impact information security and business operations. Here’s how we would approach this assessment:</p><h4><strong>UNDERSTANDING THE ORGANISATION AND ITS CONTEXT</strong></h4><p>Establishing the External and Internal issues relevant to the ISMS. The effective deployment of the ISMS will improve the security architecture of these responses, build trust in clients, and prevent potential security. The table below represents the external and internal issues related to Chester Business Ltd.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/707/1*BtjdjgvhnrFCRW-3OwSVgg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/728/1*39rFHxB5C71DH3quyowPmA.png" /></figure><h4><strong>UNDERSTANDING THE NEEDS AND EXPECTATIONS OF INTERESTED PARTIES</strong></h4><p>Identifying the needs and expectations of interested parties is necessary for CBL to effectively manage its ISMS. Identifying stakeholders, determining security requirements, and documenting these standards to verify they are consistent with ISMS objectives. will provide information about the External and Internal Stakeholders and their Requirements. Management of interested parties and legal requirements for ISMS.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/847/1*Mk17TBvu3aECTDEVHm01yw.png" /></figure><h4><strong>DETERMINING THE SCOPE OF THE ISMS</strong></h4><h4><strong>SCOPE</strong></h4><p>CBL’s Information Security Management System (ISMS) ensures governance, risk management, and compliance in information assets. It creates policies, processes, and controls to protect confidentiality, integrity, and availability, satisfying legal, regulatory, and contractual requirements. By explicitly defining the scope, auditors can comprehensively assess the ISMS’s performance in managing information security risks and meeting requirements at CBL.</p><h4><strong>BOUNDARIES AND APPLICABILITY BASED ON IDENTIFIED INTERNAL AND EXTERNAL ISSUES</strong></h4><p><strong>External Issues: </strong>— The ISMS addresses external factors such as regulatory law compliance, digital infrastructure assessment, market trends, risk assessment in the supply chain, international political considerations, and cyber threat analysis.</p><p><strong>Internal Issues: </strong>— Internal factors including organizational awareness, strategic resource management, leadership and management support, infrastructure security and management, and effective communication practices are within the scope of the ISMS.</p><h4><strong>INTERFACES AND DEPENDENCIES BETWEEN INTER-ORGANIZATIONAL ACTIVITIES</strong></h4><p>In the context of Chester Business Ltd. (CBL), identifying the linkages and connections between inter-organizational activities inside the ISMS is essential for ensuring complete and effective risk management.</p><h4><strong>CLIENT RELATIONSHIPS AND SERVICE DELIVERY</strong></h4><p>CBL provides various products and services to clients, and the implementation of these services is based on communication and collaboration with clients. Interfaces and dependencies arise only if the CBL information security process must be aligned with client requirements, contractual agreements, and industry standards to maintain the confidentiality, integrity, and availability of client data. Services include software application development, IT support services, Web hosting and development, data storage, and management.</p><h4><strong>SPECIFIC EXCLUSIONS</strong></h4><p>While the ISMS covers a broad range of organizational aspects, specific exclusions may include:</p><p>Ø Third-party systems and services are not directly controlled or maintained by CBL.</p><p>Ø Personal gadgets that employees use for work but that the organization does not own or manage by the organization.</p><p>Ø It includes all the steps required to safeguard against internal and external threats, meet legal and regulations, and meet stakeholders’ needs and expectations.</p><p>Recognizing these connections and dependencies enables CBL to establish a more complete and integrated strategy for managing information security throughout its organizational ecosystem.</p><h4><strong>INFORMATION SECURITY MANAGEMENT SYSTEM (ISMS) POLICY</strong></h4><p>CBL’s ISMS policy highlights its commitment to information security, by ensuring confidentiality, integrity, and availability of information assets. It focuses on compliance with laws, regulations, and obligations. The policy assigns responsibilities to top management and employees, and it also emphasizes the importance of continuous improvement, risk management of information security. Overall, the policy serves as a guiding document for CBL’s information security efforts, fostering a culture of security awareness and accountability across the organization. APPENDIX III refers to the Information Security Management System (ISMS) policy.</p><h3><strong>CLAUSE 5: LEADERSHIP</strong></h3><h4><strong>LEADERSHIP AND COMMITMENT</strong></h4><p>As the CIO of Chester Business Ltd (CBL), we are responsible for implementing the Information Security Management System (ISMS), so we must comprehend and meet the ISO 27001:2022 standards. By meeting these requirements, we demonstrate our dedication to information security leadership and making sure our ISMS is strong effective, and in line with CBL’s corporate objectives. APPENDIX IV: leadership and commitment table</p><h4><strong>POLICY</strong></h4><p>As a Chief Information Officer of CBL, in charge of implementing the Information Security Management System (ISMS), we would describe Clause 5.2 as follows. Overall, the information security policy is a foundational document that expresses CBL’s commitment to safeguard its information assets and establishes the framework for the implementation of ISMS. It ensures coherence with organizational objectives and regulatory standards. APPENDIX V: Establishment and communication of the policy.</p><h4><strong>ORGANIZATIONAL ROLES, RESPONSIBILITIES AND AUTHORITIES</strong></h4><p><strong>a) Adherence to ISO 27001 Standards:</strong> Top management including us as the CIO, is responsible for ensuring that the ISMS meets the requirements established in ISO 27001. This includes managing the ISMS’s implementation, maintenance, and continuous improvement to ensure that it meets the standards criteria.</p><p><strong>b) ISMS Performance Reporting:</strong> It is the responsibility of the CIO and other key executives to report to the authorities about the performance of ISMS. This includes sending regular updates on the efficiency, and effectiveness of ISMS, as well as any areas for improvement that should be managed or resolved.</p><p>Furthermore, top management can assign extra duties and responsibilities for reporting ISMS performance. This might involve assigning certain staff or departments to monitor key performance, conducting internal audits, and enabling channels of communication for reporting security breaches. Clearly defining and communicating information security roles, responsibilities, and authorities, CBL ensures transparency, and effective management thereby contributing to the organization’s overall security posture and durability to cyber threats.</p><h3><strong>CLAUSE 6: PLANNING</strong></h3><h4><strong>ACTIONS TO ADDRESS RISKS AND OPPORTUNITIES</strong></h4><p>This clause highlights the need for initiative-taking risk management and opportunity identification inside the ISMS. Organizations must examine a range of factors, including challenges and requirements outlined in the standard when determining risks and opportunities relevant to their information security goals. The goal is to ensure that the ISMS achieves its desired results, prevents, or reduces unwanted consequences, and promotes continuous development.</p><h4><strong>GENERAL</strong></h4><p>Clause 6.1.1 describes the steps that CBL must take to address risks and opportunities within its ISMS. Appendix VI will show the details of the steps in addressing risk and possibilities. It includes:</p><p>a) Addressing issues and requirements</p><p>b) Risk Identification</p><p>c) Risk Management</p><p>d) Action planning</p><p>e) Integration and Execution</p><p>f) Evaluation</p><h4><strong>INFORMATION SECURITY RISK ASSESSMENT</strong></h4><p>Risk assessment is a systematic process for identifying, analysing, and evaluating potential risks affecting an organization’s objectives, operations, or projects. It aids in prioritizing risks, allocating resources effectively, and implementing controls to mitigate risks.</p><p><strong>a) RISK CRITERIA ESTABLISHMENT:</strong> CBL will establish and maintain information security risk standards, such as acceptance of risk and risk assessment process. These standards will ensure a consistent and reliable risk assessment process.</p><p><strong>b) RISK ASSESSMENT CONSISTENCY:</strong> CBL will ensure that repeated risk assessment generate consistent, valid, and comparable outcomes. This includes defining the risk assessment technique and ensuring that qualified individuals conduct evaluations.</p><p>c) <strong>RISK IDENTIFICATION AND ANALYSIS:</strong></p><p>Ø Identification: CBL will use a risk assessment method to identify information security risks related to loss of privacy, reliability, and accessibility of data within the scope of ISMS. Risk owners will be identified for every risk that is identified.</p><p>Ø Analysis: CBL will assess the potential implications and likelihood of occurrence for the highlighted risks. This analysis will help to estimate the risk level associated with each identified risk.</p><p>d) <strong>RISK PRIORITIZATION AND EVALUATION</strong></p><p>Ø Evaluation: CBL will assess the information security risks by comparing the results of the risk analysis to the risk criteria established in Clause 6.1.2a. This evaluation will assist in determining the importance of each risk to the organization’s risk tolerance and objectives.</p><p>Ø Prioritization: Based on the assessment, CBL will prioritize the identified risks for risk treatment. Risks will be prioritized depending on their level of relevance and the organization’s ability to successfully manage them.</p><p><strong>e) RISK ASSESSMENT DOCUMENTATION PROCESS: </strong>CBL will keep all documented information concerning the information security risk assessment process. This documentation will include information on risk criteria, assessment results, risk owners, and prioritized risks.</p><h4><strong>INFORMATION SECURITY RISK TREATMENT</strong></h4><p>A risk treatment plan is a strategic plan for an organization to address identified risks, outlining actions, timelines, resources, and monitoring effectiveness. It serves as a roadmap for proactive risk management and resilience against potential threats. Appendix VII A shows the detailed Risk treatment steps in the context of CBL. Appendix VII B, C, D show risk assessment, treatment and Annex A (SoA), It includes:</p><p>a) Risk treatment option.</p><p>b) Controls identification</p><p>c) Annex A controls.</p><p>d) Statement of applicability</p><h4><strong>INFORMATION SECURITY OBJECTIVES AND PLANNING TO ACHIEVE THEM</strong></h4><p><strong>Establishment and Characteristics of Information Security Objectives:</strong></p><p>The CBL will establish information security objectives at all appropriate departments and levels within the company. The information security objective is aligned with the information security policy.</p><p><strong>Documented Information Retention</strong></p><p>CBL shall maintain documented information on defined information security objectives. This documentation will act as a reference point for tracking progress and evaluating the ISMS efficacy over time.</p><p><strong>Information Security Objectives Planning</strong></p><p>To meet its information security objective CBL will determine:</p><p>Ø What specific actions must be made to achieve the objectives?</p><p>Ø What resources are needed like technology, and budget to support the actions?</p><p>Ø Who is in charge for executing and overseeing each step?</p><p>Ø When the steps will be finished with credible dates and goals.</p><p>Ø How these results are evaluated, to ensure that they effectively contribute to accomplishing the information security objectives.</p><p>This organized strategy ensures that CBL’s ISMS is always focused on continuous improvement and adaptation to changing security threats.</p><h3><strong>CLAUSE 7: SUPPORTS</strong></h3><h4><strong>RESOURCES</strong></h4><p>In all organizations, resources are especially important be it human, financial, or material (Technology, equipment, facilities). CBL as an organization is not left out as there is the for resources to establish and maintain its ISMS.</p><h4><strong>COMPETENCE</strong></h4><p>To implement a sustainable ISMS, CBL needs to have a standard requirement for those employed in certain roles in the various departments, IT, Facilities, Research, etc. There is the need for employees to be properly screened before being brought to the organization to assume duties. Technical skills, Aptitude skill, experience, certifications, and education level should be assessed and evaluated. Importantly, there should be constant and continuous training on relevant Information security risks both on a general level and specific level as it relates to their job roles.</p><h4><strong>AWARENESS</strong></h4><p>CBL will ensure that her staff are properly aware of the dangers of cybersecurity breach in business continuity and how it relates to individuals. Employees would be properly trained to understand the Information security policy and to recognise common cyberattacks as phishing, malware attacks, password protection and web attacks, regardless of their department and background.</p><h4><strong>COMMUNICATION</strong></h4><p>The Board of CBL would establish and approve dedicated communication channels for exchange of information and facilitate proper partnerships with external teams. Internal communication within the organization would also be maintained to ensure smooth operations and business continuity.</p><h4><strong>GENERAL</strong></h4><p>CBL will properly keep record of the ISMS and policies, to be reviewed and updated with the changing Business environment and current security trends. The document will contain policies, inventories, network diagram, business physical facilities, stakeholders etc. The ISMS would be available as both hard and soft copies and easily accessible.</p><h3><strong>CLAUSE 8: OPERATION</strong></h3><h4><strong>OPERATIONAL PLANNING AND CONTROL</strong></h4><p>CBL will see to the implementation, procedure, planning, and control needed for risk management and to meet the required information security requirements for effective and efficient ISMS.</p><h4><strong>INFORMATION SECURITY RISK ASSESSMENT</strong></h4><p>CBL will conduct risk assessments regularly to identify business changes that may have affected the most recent risk assessment. This would enable CBL to implement necessary risk treatment.</p><h4><strong>INFORMATION SECURITY RISK TREATMENT</strong></h4><p>CBL will establish and implement the risk treatment plan when due and the results will be</p><p>properly documented.</p><h3><strong>CLAUSE 9: PERFORMANCE EVALUATION</strong></h3><h4><strong>MONITORING, MEASUREMENT, ANALYSIS AND EVALUATION</strong></h4><p>The effectiveness of the ISMS would be reviewed and analysed quarterly based on metrics and KPIs. The result of the analysis would be made available to the CBL board for further action and resource allocation where needed.</p><h4><strong>INTERNAL AUDIT</strong></h4><p>CBL will set up/employ an Internal Auditor to whom will constantly ensure the aims and objectives of the ISMS are well adhered. The Auditor will also document his results as a report stating his findings and areas for action.</p><h4><strong>MANAGEMENT REVIEW</strong></h4><p>There will be Consistent Management reviews to address internal and external reports, results, feedback, and security issues that might affect the efficacy of the ISMS. Decisions are then made to ensure the improvement of the ISMS.</p><h3><strong>CLAUSE 10: IMPROVEMENT</strong></h3><h4><strong>NON-CONFORMITY AND CORRECTIVE ACTION</strong></h4><p>CBL would review non-conformity to minimize the impact, CBL would also respond quickly to them and implement measures to control and correct or fix the problems. In addition, it is necessary to keep track of process improvement by establishing and maintaining documented data.</p><h4><strong>CONTINUAL IMPROVEMENT</strong></h4><p>The effectiveness, impact, and effect of the ISMS would be continually improved, this improvement cannot be made without conducting proper evaluation and reviews of the efficacy of the ISMS. This continuous improvement helps to maintain ISMS effectiveness in a changing business environment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/607/1*A1BRioRuf8hbasf6SwQdOg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/714/1*3w85K6z3dpCoCh4Kggywbg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/730/1*s4zoQZncKEXoLVqw11cxaQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/706/1*-5U_7k2x8VsZPxwPfBtvxA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/706/1*qqu02VqrGYJKD4HOKX6lIg.png" /></figure><h3><strong>ISMS POLICY</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/731/1*ibZFkVfY1a1MekWJteg4sQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/693/1*GPZVbLuBos3-7i0xd59Xxg.png" /></figure><h3><strong>LEADERSHIP &amp; COMMITMENT TABLE</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/856/1*dUTEM-1MVmkeGSayNwx7Jg.png" /></figure><h3><strong>ESTABLISHMENT &amp; COMMUNICATION OF POLICY</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/856/1*6Lr52fKhD_Rh2pW7iA54Xw.png" /></figure><h3><strong>STEPS IN ADDRESSING RISK</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/840/1*OV_NXkz89g0iVfVcJaGI2A.png" /></figure><h3><strong>RISK TREATMENT STEPS</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/839/1*DurMlg4YabjtP-s1Zg0z-w.png" /></figure><h3>CONCLUSION</h3><p>The strategic implementation of an Information Security Management System (ISMS) at Chester Business Limited reflects our unwavering commitment to protecting our digital infrastructure and upholding the highest standards of cybersecurity. By integrating industry-leading tools like IRIUS Risk into our threat modeling process, we’ve enabled a proactive and structured approach to identifying, assessing, and mitigating potential threats across the organization.</p><p>Through clearly defined roles, robust policies, continuous monitoring, and a strong leadership commitment, CBL ensures that information security is deeply embedded in our operations and culture. From risk treatment planning to internal audits and continual improvement cycles, our ISMS serves as a dynamic, responsive system that evolves alongside the threat landscape.</p><p>In an era where information is one of the most valuable assets, CBL’s ISMS not only supports regulatory compliance but also fosters trust, operational resilience, and long-term business continuity. Our journey demonstrates that cybersecurity is not a one-time task it’s an ongoing commitment to excellence, vigilance, and innovation.</p><p><strong>Disclaimer</strong><br>The names, organizations, and scenarios presented in this report are entirely fictional and are used solely for illustrative and educational purposes. (CBL) and the analyst identifier J111855 do not represent any real individuals or companies. Any resemblance to actual persons, living or dead, or actual entities, past or present, is purely coincidental.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bc18ada3ebab" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[RISK ASSESSMENT, SECURITY CONTROLS & RISK TREATMENT PLAN (ISO27001)]]></title>
            <link>https://medium.com/@adeoyedavid55/risk-assessment-security-controls-risk-treatment-plan-iso27001-f0ce14492665?source=rss-935cded74d48------2</link>
            <guid isPermaLink="false">https://medium.com/p/f0ce14492665</guid>
            <dc:creator><![CDATA[Adeoye Iyanuoluwa David]]></dc:creator>
            <pubDate>Thu, 10 Jul 2025 19:18:06 GMT</pubDate>
            <atom:updated>2025-07-10T19:18:06.239Z</atom:updated>
            <content:encoded><![CDATA[<p>In today’s rapidly evolving digital landscape, maintaining robust information security is not just a best practice it’s a necessity. As part of an internal review at CBL, a comprehensive ISO 27001:2022-based security compliance assessment was conducted to evaluate the organization’s current information security posture. The assessment focused on four key control areas: <strong>Organizational</strong>, <strong>People</strong>, <strong>Physical</strong>, and <strong>Technological</strong>. While there are several commendable practices already in place, significant gaps were identified ranging from the absence of a formal information security policy to weak physical access controls and insufficient technological safeguards. This blog post dives into the findings and offers actionable recommendations to strengthen CBL’s security framework and lay the groundwork for future ISO certification.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CtXKhhFZRphKnv7E_sDlrQ.jpeg" /></figure><h3>RISK ASSESSMENT</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/816/1*sl1I6TG7M0AIAc60CPlGDA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/809/1*W6lkr-3N2lTC782Ill855g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/824/1*iJEC1UfIVEfh4u5yosR6Xw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/692/1*IOZYVwEhDJY8Oys1YTyidQ.png" /></figure><h3><strong>RISK TREATMENT PLAN</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/696/1*KRLsBoZ4fyDpL2iFCu-a4w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/697/1*-w9SjHtKlGZLjw8Wbo1F-w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/696/1*LYOC1QznCCRnKSvp3Gc_NA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/726/1*fHIBxpoqf766Dpg7vJfoeQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/693/1*tDdMWJ0jCBU5geaDTGD9cA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*NG7XmvJVNq3M9ozYOanrPQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*PNcEgs9SojstHYsRqWy7tg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/689/1*hwxWmqZ7CTQe8g4EFoY49Q.png" /></figure><h3><strong>STATEMENT OF APPLICABILITY (ANNEX A)</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/687/1*86ElB6sLz0yQqed37H2z_w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/703/1*I9FE5sZvzVSAHLA6M5BF7g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/675/1*2y9Vkvd0ZNndtjClu-2U0w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/705/1*qAlHsPncHWQzsktPnuu8mA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/701/1*EMTQCEP3BfxcEkY8olGGyg.png" /></figure><h3>CONCLUSION</h3><p>The assessment reveals that while CBL demonstrates several good practices, such as the use of MFA, regular software updates, and structured access controls, there remain critical areas requiring immediate attention. Organizationally, the absence of core information security policies, inadequate physical security controls, lack of human resource governance, and technological weaknesses all increase the organization’s risk footprint. Addressing these gaps is not just about compliance but about strengthening CBL’s ability to protect its assets, employees, and customers. Though ISO certification was not the primary goal of this assessment, aligning with ISO 27001 standards will place CBL on a stronger trajectory toward operational resilience and competitive advantage in a security-conscious marketplace.</p><p><strong>Disclaimer</strong><br>The names, organizations, and scenarios presented in this report are entirely fictional and are used solely for illustrative and educational purposes. (CBL) and the analyst identifier J111855 do not represent any real individuals or companies. Any resemblance to actual persons, living or dead, or actual entities, past or present, is purely coincidental.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f0ce14492665" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ISO 27001 SECURITY COMPLIANCE ASSESSMENT]]></title>
            <link>https://medium.com/@adeoyedavid55/iso-27001-security-compliance-assessment-8226b98204e9?source=rss-935cded74d48------2</link>
            <guid isPermaLink="false">https://medium.com/p/8226b98204e9</guid>
            <dc:creator><![CDATA[Adeoye Iyanuoluwa David]]></dc:creator>
            <pubDate>Thu, 10 Jul 2025 19:07:26 GMT</pubDate>
            <atom:updated>2025-07-10T19:07:26.139Z</atom:updated>
            <content:encoded><![CDATA[<p>In today’s rapidly evolving digital landscape, maintaining robust information security is not just a best practice it’s a necessity. As part of an internal review at CBL, a comprehensive ISO 27001:2022-based security compliance assessment was conducted to evaluate the organization’s current information security posture. The assessment focused on four key control areas: <strong>Organizational</strong>, <strong>People</strong>, <strong>Physical</strong>, and <strong>Technological</strong>. While there are several commendable practices already in place, significant gaps were identified ranging from the absence of a formal information security policy to weak physical access controls and insufficient technological safeguards. This blog post dives into the findings and offers actionable recommendations to strengthen CBL’s security framework and lay the groundwork for future ISO certification.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0yTYeZPsuRtsiMc0g2nl1w.jpeg" /></figure><h3><strong>EXECUTIVE SUMMARY</strong></h3><p>This report is to present the result of the security compliance assessment for CBL using ISO27001:2022 controls.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/897/1*u90EZCmplBV2H0aO8VUaKA.png" /></figure><p>This report describes the findings of the security compliance assessment, the strong points and weakness found in the organization’s security system. Most importantly, recommendations for improvement in Information security systems would be outlined. From the assessment there is the need for CBL to implement an Information security policy as mentioned in the Organizational controls, the existence of this policy would address security risks identified in the organization, such as the possibility of ransomware attacks and loss of data. The Physical controls of the organization needs a number of improvements ranging from installation of more cameras, upgraded access controls, changes to office floor plans among others. The people controls equally needs some improvements, this might be due to the absence of a Human capacity management with a proper HRM team in place it would be easier to implement majority of the controls in this group. Technological controls, has some best practice in place due to the monitoring of Networks and the upgrade and updating of security software and applications, however some improvements are also needed in this group, there’s the need to be well prepared for information security measures to benefit of the convenience and purpose of information technology.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/866/1*Ats4DoPMyDmnP8k6OqOY4g.png" /></figure><h3><strong>OBJECTIVES AND SCOPE</strong></h3><p>This main aim of this assessment is to understand the IT system of CBL and not to necessarily towards being ISO complaint, therefore some common terms of ISO compliance such as “shall” and “should” have not been seriously worked with in this assessment. The assessment objective is to give the organization a general overview of what the IT structure is at the moment and to identify areas needing improvements.</p><p><strong>Organizational controls:</strong> The leadership structure, delegation of responsibilities and segregation of duties was assessed. The existence of necessary topic related policies, procedures and the implementation and compliance with these processes was also assessed.</p><p><strong>People controls:</strong> Human resource management was also assessed, the selection process, disciplinary process and more. The relationship between humans and technology, the existence of processes and procedures to guide this relationship to ensure Information system security was assessed.</p><p><strong>Physical controls:</strong> CBL’s physical security was critically assessed, security measures put in place to secure not only the staff but also the equipment of the organization were reviewed.</p><p><strong>Technological control</strong>: CBL’s network, servers and workstations were also assessed, the security measures in place, the maintenance and monitoring process of the networks was also looked into.</p><h3><strong>KEY FINDINGS</strong></h3><p><strong>ORGANIZATIONAL CONTROLS</strong></p><p>From findings, CBL lacks an Information security policy, hence making the implementation of some other controls quite impossible and some other policy and procedures become inevitably undocumented. Examine the undocumented BYOD policy, this opens the organisation to more security risk, ransomware and loss of data that could result in stringent financial sanctions. The undocumented policy on the use of external storage device, the use of open source remote application to login to company’s network are some of the ripple effects and risks of the lack of Information security policy that is missing in the organization. Also lacking is a well-defined allocation of roles and segregation of duties. Project management should be in sync with the IT department rather than the Head of Business. CBL is also open to possible data leak with the absence of a dedicated channel of communication with collaborators, while the communication has been established, it should be more secured. The organization has in place an inventory of assets, however it can be found that the inventory is not well detailed has it is missing details of the software installed on the assets, this increases the organization’s attack surface.<br>There is missing an appropriate procedure for information labelling in the organization.</p><p>CBL has in place Access control measures (ACL, MFA) to address this, Staff are well trained but the physical access control put in place is weak and porous. The organization does not have documentations in place to manage their relations with product suppliers such as CISCO that supplied their switches and router, and the organization is generally silent when it comes to suppliers relationships. The organization has made an attempt at maintaining readiness for business continuity with the existence of backup system for their data, findings shows this might not be a step in the right direction towards business continuity as the backed-up data are being stored on the main network, this makes the backup to be as equally vulnerable as the main data.</p><p>Security software being put in place by the organization generates and save logs, however it is quite unclear if the business does much with these logs, the organization does not have spelt out plans on incident management, and the logs are not being assessed to determine events and incidents and definitely no incident response plan.</p><p>In conclusion, it is good practice that the organization trains staff to identify social engineering attacks, data classification and others. Workstations are properly assigned, monitored and managed making it easy to manage identities or asset owners. Servers are configures on need to know basis which is a good practice, MFA are in place and patches are regularly updated and the use of VPN for secure remote connection.</p><h4><strong>PEOPLE CONTROL</strong></h4><p>It cannot be found that proper screening and checks are being carried out on staff before they join CBL, same can be said for the case of contractual agreement with the staff, the lack of documented procedure for disciplinary actions of staff has also been left unaddressed by CBL and also responsibilities for termination/change of employment has not been put in place the absence of HR department makes it quite difficult for these controls to be met. CBL lacks non-disclosure agreement with staff and collaborators, this leaves the organization at risk of data leak and possible financial sanctions.</p><p>It is however a good practice that security personnel are properly screened with DBS checked and only Government recognised security companies are being engaged.</p><h4><strong>PHYSICAL CONTROL</strong></h4><p>The physical security also needs some improvements, the open and direct path from various parts of the office to the server and switch rooms pose a major security risk, and there is no mention of the use of access controls such biometrics or key cards to these rooms, which makes them easily accessible for anyone. The porous physical security also poses a threat to the equipment, the idea of them being sited securely is out of the window, also cables security has been brought to zero as just anyone can gain access to them and cause any sort of damage.</p><p>CBL lacks adequate cameras for continuous monitoring of the office premises, not every side of the office is being well monitored, and these however makes the organization an unsecure area for working. In addition the organization has not made provision for protection against physical and environmental threat, while this might not be regular occurrence it is necessary to have them in place.</p><p>The use of external devices by staff for storing and moving data shows CBL does not have in place a proper storage media, the organization does not have in place any form of support facility in the case of failure or disruption such as power failure.</p><p>Good practice found here is the clear marking of restricted areas and the wearing of identification tags within the office premises.</p><h4><strong>TECHNOLOGICAL CONTROL</strong></h4><p>Observing the organization’s network dossier, while endpoint security software, anti-virus and anti-malware software are installed on workstations, the personal devices of staff that are being used to connect to company’s network are left out and pose security risk. The use of technology and human resources are not properly managed in the organisation, the role of staff are not properly defined, asset inventory is not properly kept, access to use open source code by the developer, lack of proper management of technical vulnerability information all shows poor technology capacity management. The absence of a proper media storage has made it difficult for information deletion and data leakage prevention control to be implemented. The networks are not properly segregated, domain controller and file server are using the same server this could affect availability as a part of CIA triad.</p><p>Good practices identified here are, ACLs are being configured on a need to know rule, firewall rules control traffic flow, and MFA are being used and strong password policies. Network are being regularly monitored and there is the existence of network documentation, firmware, firewalls and patches are updated.</p><h3><strong>RECOMMENDATIONS</strong></h3><h4><strong>ORGANIZATIONAL CONTROLS</strong></h4><p>Information security policy and topic specific policies should be put in place following necessary procedures, this should address BYOD, use of external storage devices, use of open source remote application and the use of open source codes by developers, segregation of roles and duties within the organization among other things, this would help reduce the likelihood of data breach in the organization. Security procedures and guidelines which should include related operations, information, person, software, facilities, and services.</p><p>A secure and dedicated communicated channel has to be devised and put in place to manage the communication with external collaborators. The organization needs to keep a more central and detailed inventory, this should include all assets, asset owners, software, websites and other, this helps the organization manage all assets and reduce attack surface. The organization should create and maintain a supplier relationship document for Cisco ASA 5505, Cisco SG200–24, and other third part products and services to manage security risk. CBL should review their backup method and make it align with the 3–2–1 backup rule, also the backup needs to be regularly tested, it is important that clear recovery scenarios of the organization’s operations are defined, implemented, but above all rigorously tested periodically. Log monitoring, assessment and storage should be included in the IT department duties so as to identify what constitute what makes an event and incident.</p><h4><strong>PEOPLE CONTROL</strong></h4><p>There should be a HR department doesn’t necessarily have to be a large team, they are to handle, screening of new staff, drafting contractual agreement, disciplinary actions, termination of employment and drafting of non-disclosure agreement. They will also help to organize staff trainings and communicate Information security policies to staff in the right and proper method. The employees and third party should follow the organization’s security policies, receive appropriate awareness training and regular updates in organizational policies and procedures, as relevant for their job roles.</p><h4><strong>PHYSICAL CONTROL</strong></h4><p>Generally speaking the physical security of CBL needs to be improved, the open paths that leads to the server and switch rooms should be closed and access controls should be installed to include biometrics or key cards usage, this protects the equipment cables and also prevent possible malware attacks. IT centre should be rated security level A, These areas only be allowed with limited person who need to perform work in those areas to access, any access should scan availability employee ID and correct password. More cameras should be installed to cover the enter premises both inside and outside of the office, security cameras should equally be properly monitored. Individuals using the conference room should be properly vetted before gaining access into the facility.</p><h4><strong>TECHNOLOGICAL CONTROL</strong></h4><p>Access control policies should be formally documented, also incident management procedures should be formalized and well documented. The networks/servers should be properly segregated to ensure availability, For physical assets, services and third party, network service, and data centres, availability is the most important risk objective.</p><h3><strong>CONCLUSION</strong></h3><p>From the assessment result it can be seen that CBL needs to make some improvements in its Information security, while this assessment is not towards being ISO compliant, it is recommended to work towards being ISO certified. ISO27001 can be particularly applied to all industry sectors, organizations that are ISO27001 compliant would make their customers have more confidence in them and they can get more business chance in the competitive global market.</p><h4><strong>ORGANIZATIONAL CONTROLS</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0jxgz_Qem3hqI4H0SymAbQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ymw6QwsUt01GYRK54Ibhrw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*72-XWITFhNZYUCeUYaPLNg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JLvS-l898W9MI6awnBCezw.png" /></figure><h4><strong>PEOPLE CONTROLS</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PnG6LXDqbAhKNGSBXUXHvg.png" /></figure><h4><strong>PHYSICAL CONTROLS</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WHm2zMijpXaLTlFUSnBSRQ.png" /></figure><h4><strong>TECHNOLOGICAL CONTROLS</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uS3BGgT_i3iHOcSJ3ZYlDg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pFRks_8ynPzRknfBGr0scA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dL4ZNBW2qSt8j68w1XS5HQ.png" /></figure><h4>CONCLUSION</h4><p>The assessment reveals that while CBL demonstrates several good practices, such as the use of MFA, regular software updates, and structured access controls, there remain critical areas requiring immediate attention. Organizationally, the absence of core information security policies, inadequate physical security controls, lack of human resource governance, and technological weaknesses all increase the organization’s risk footprint. Addressing these gaps is not just about compliance but about strengthening CBL’s ability to protect its assets, employees, and customers. Though ISO certification was not the primary goal of this assessment, aligning with ISO 27001 standards will place CBL on a stronger trajectory toward operational resilience and competitive advantage in a security-conscious marketplace.</p><p><strong>Disclaimer</strong><br>The names, organizations, and scenarios presented in this report are entirely fictional and are used solely for illustrative and educational purposes. (CBL) and the analyst identifier J111855 do not represent any real individuals or companies. Any resemblance to actual persons, living or dead, or actual entities, past or present, is purely coincidental.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8226b98204e9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[DIGITAL FORENSICS]]></title>
            <link>https://medium.com/@adeoyedavid55/digital-forensics-37bd631e88a4?source=rss-935cded74d48------2</link>
            <guid isPermaLink="false">https://medium.com/p/37bd631e88a4</guid>
            <dc:creator><![CDATA[Adeoye Iyanuoluwa David]]></dc:creator>
            <pubDate>Wed, 09 Jul 2025 19:42:35 GMT</pubDate>
            <atom:updated>2025-07-09T19:42:35.265Z</atom:updated>
            <content:encoded><![CDATA[<p>In today’s hyper-connected world, data breaches are an ever-present threat to organizations of all sizes. When a suspected breach occurred at TSH the need for a thorough digital forensic investigation became urgent. Tasked with uncovering the root cause, identifying the impact, and recommending security improvements, this investigation highlights how digital forensics plays a critical role in incident response. In this blog post, we’ll walk through the forensic process used to examine the breach at TSH, including evidence gathering, memory and disk imaging, static and dynamic malware analysis, and the tools employed throughout. We’ll also explore the potential attack vectors, assess the business impact, and share practical recommendations to help organizations like TSH strengthen their cybersecurity posture and prevent future incidents.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bPpU5SF9To2dlWwZ3Pa_ww.jpeg" /></figure><h3><strong>INTRODUCTION</strong></h3><p>This technical report is to investigate a data breach at TSH, a 35 staff company that builds software. TSH has suspected a possible data breach and has contracted CDFnS to conduct an investigation. This report explains the investigation process which include understanding the breach, what was the cause of the breach and what are the possible recommendations to prevent future incidents. What i will be also doing in this report is to explain the investigation process, digital forensic process, static analysis and dynamic analysis using industry-standard tools, i will also discuss the effect of this breach on TSH and give possible remediation measures.</p><h3><strong>EXPLAINING DIGITAL FORENSIC</strong></h3><h4><strong>DIGITAL FORENSIC PROCESS</strong></h4><p>Digital forensics process is the participation of computer science and digital technology in investigation procedures to gather digital evidence of a crime, this helps protect an evidence and give reliable results. Using the process by Zatyko it will be possible to investigate the data breach at TSH, understand the cause and recommend prevention practices against future incidents.</p><p><strong>Get Authority:</strong> The important thing here is to secure relevant authorization, from TSH board and legal team to carry out digital forensics and ensure you comply with GDPR.</p><p><strong>Chain of Custody: </strong>Maintain the integrity of the captured evidence by documenting the collection, handling, movement and storing of the evidence.</p><p><strong>Imaging and Hashing:</strong> Create a clone of the original systems this is a digital forensic best practice so as to preserve the original evidence from being destroyed during investigation. In the case of TBH we will create an image copy of their machines. Hashes will be calculated to ensure integrity.</p><p><strong>Validated Tools:</strong> Make use of forensics tools that are reliable and industry recognized for investigation, tools should be up-to-date and must be validated to get the job done.</p><p><strong>Repeatability (Quality Assurance): </strong>Proper documentation of digital forensic steps and methodologies must be enabled so as any other investigator can replicate these same steps and get same results and findings.</p><p><strong>Analysis:</strong> Analyse logs, images, network traffic and other evidence that indicates compromise and vulnerabilities. Conduct dynamic analysis and static analysis of these evidences using the right tools.</p><p><strong>Reporting:</strong> Document an easy to understand report by diverse audiences. A fully detailed report that contains the findings, methodology, conclusion and also recommend solutions for future security improvement.</p><p><strong>Presentation:</strong> Simple and easy to understand presentation of the findings and conclusion for the appropriate stakeholders (board, legal team and court).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/903/1*-HZ5zfWqhh4UO8wIycdsZg.png" /></figure><h4><strong>POSSIBLE SCENARIOS</strong></h4><p><strong>Insider Threat:</strong> A current TSH employer may have intentionally misuse their privileges to compromise the organization’s data confidentiality, integrity or availability.</p><p><strong>External Attack:</strong> An attacker outside of TSH may have gained access into either the client windows machine. The attacker after gaining access can easily move around in the network and gain access to sensitive data.s</p><p><strong>Brute Force Attack: </strong>Thousands of logon attempts made from the windows 10, shows possible BFA.</p><p><strong>Supply Chain Attack: </strong>One of the third-party vendors software or services TSH uses might have been compromised, giving an attacker unauthorized access into TSH network and access to sensitive data and compromised the CIA.</p><p><strong>Malware Infection:</strong> TSH maybe be experiencing a malware attack which has entered their network through numerous means including through email attachments, malicious URLs. The malware could have easily spread across the entire network installing its C2.</p><p><strong>Social Engineering Attack:</strong> Being one of the most common form of attack we cant rule out the possibility of this attack, tactics such as phishing might have been used to deceive a staff to gain access into TSH data or systems.</p><p><strong>Weak Security Controls:</strong> TSH’s security team might have been a bit lazy in monitoring and maintaining their security infrastructure, weak passwords, unused ports or unpatched vulnerabilities might have been accessed by an attacker to gain unauthorized access and compromise the CIA.</p><h4><strong>INFORMATION GATHERING</strong></h4><p>Most Cybersecurity action plan starts with Information gathering(Reconnaissance), same goes for digital forensics. To investigate TSH’s environment we need to gather information as this is important to any digital forensic investigation. TSH’s network dossier and security infrastructure document should be requested for, also configuration and path documentation of their windows machines. This helps to give an overview of the IT system and identify attack surface. Basic information about the incident should also be collected like, date, time, data involved, machine involved, owner of the machine, logging capabilities. Gather information about the organization’s backup, do they have a backup procedure in place, if they do what is the backup frequency, how is the storage done, where is it stored and what is the recovery plan. Understand the compliance or legal rules that the organization abide by that is related to digital forensics, so as to make sure the investigation is compliant with the laws. Look into user account and user privileges, who has access to what and who doesn’t, this will allow to identify unauthorized or misuse privileges. Finally, understand the company’s digital forensics policy as mentioned by NIST(2006).</p><h3><strong>TOOLS USED</strong></h3><h4>STATIC ANALYSIS TOOLS</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/649/1*Ki_iR8cXO0zcFjpOhxe1OQ.png" /></figure><h4><strong>DYNAMIC ANALYSIS TOOLS &amp; WINDOWS INBUILT TOOLS</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/660/1*zzF06v3jvb-lW0NCH3Krcw.png" /></figure><h3><strong>IMPACT ON THE BUSINESS</strong></h3><p>In most cases a breach or intrusion usually have a negative effect on a business, however the weight of this effect is usually determined on the severity of the intrusion and what data was accessed this will be detected as the digital forensic investigation proceeds. It should be noted that the nature or behaviour of malware plays a major role in how it affects the business, if the malware has spreading properties then downtime is inevitable and how fast the malware spreads will also affect the length of the downtime. Other impact of the intrusion on TSH can range from financial loss, legal sanctions, data loss and operational disruptions. It is expected that the breached devices should be disconnected from the network and isolated, and through check should be done to ensure the malicious properties have not spread across the network. It is expected that whatever investigation would be carried out in TSH should be as discrete as possible to prevent reputation damage and loss of customers.</p><p><strong>WINDOWS SYSTEM MEMORY AND DISK IMAGING</strong></p><p>This section is where the processes for disk and memory imaging for the TSH’s machines will be done as a part of the digital forensic investigation process. Defines disk image as creating a forensically sound copy of a disk and compressing the image to form a file, this image can then be stored on dissimilar media for archiving and future possible restoration. Disk imaging is to allow for investigation to be carried out without compromising the original evidence, a good disk imaging tool will not alter the original copy of the evidence.</p><p><strong>WHY MEMORY AND DISK IMAGING</strong></p><p>In carrying out digital forensic evidence needs to be gathered to be analysed and possibly for legal purpose. It is important to however preserve the original evidence and protect it from alteration, compromise, damage and corruption of data therefore it is beneficial to create a copy of the original evidence, this copy will then be worked with. Proper collection and preservation of evidence guarantee the integrity of the evidence. Analysing memory and disk images can help uncover traces left by an attacker, discover presence of malwares and other attacker’s activities.</p><p><strong>PRECAUTIONS TAKEN</strong></p><p><strong>Image taken on external drive: </strong>When taking images it should be saved on external storage device to ensure the evidence is not contaminated or tampered with.</p><p><strong>External Storage Device Type:</strong> Compactible storage device should be used, not all storage device are compactible with all Operating systems, also the size of the storage device should be put into consideration. In the case of TSH a storage device with NTFS file system is advised.</p><p><strong>Maintain Chain Of Custody:</strong> Every step of transfer or handling of the acquired image must be established and maintained, this is to make sure the evidence integrity is maintained.</p><p><strong>Make Forensic Copies: </strong>Working with forensic copies of the original data is advised, to protect the original copy from contamination such as accidental remodifications.</p><p><strong>Confirm Integrity:</strong> Integrity checks like hash checking should be done on the images to ensure the images were gotten from the right sources.</p><p><strong>Document the process: </strong>All relevant details should be documented even before anything is started, details like date, time, location, device information etc should be properly documented.</p><h3><strong>MEMORY IMAGING (DumpIt) and ANALYSIS (Volatility)</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/962/1*xCB5EAr-Mm2fTkH7T_F6bA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/959/1*Zhv83Afy1RB7HacNbFiGJA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/622/1*WExEHATejTOqF9JcF4B7Ug.png" /></figure><h3><strong>FTK IMAGER &amp; AUTOPSY</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/903/1*STY4OfhFVFQGHhm4OQPyWg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/903/1*dBADIeo2WwEqYfCfIcyzpg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/903/1*tR7Qgrf59qR8LJ1i4WXyHQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/905/1*ZX_PLgGdm3vy7mDRFQ3d-g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/920/1*QJTlYkg3gLfwmEHnnXuABg.png" /></figure><h3><strong>AUTOPSY ANALYSIS</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/903/1*9sww-W82HeGgfPyy_9Q0pQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/916/1*n2snuS9CfxF1Uh-hjoUqDw.png" /></figure><h3><strong>MALWARE ANALYSIS</strong></h3><p><strong>DEFINITATION OF STATIC AND DYNAMIC ANALYSIS</strong></p><p>Static analysis is the process of analysing a malware without actually running it. Static analysis can be said to be safe because the malware is analysed without the actual execution of the malware sample. Static analysis also deals with debugging malicious document, the static code analyser goes ahead to check the content of the document against some predefined rules and existing malware document hashes.</p><p>Dynamic analysis on the other hand involves malware sample being observed while running the sample in a controlled environment. The registry key is malicious changed when the malware executes and it takes over the operating system and changes everything on the operating system.</p><p><strong>BENEFITS AND LIMITATIONS OF STATIC ANALYSIS</strong></p><p>An advantage of static analysis is the ability to use it create signature-based detection rules which is used by IDS or AV. The use of static analysis for code analysis is also another pro, malware codes are reverse engineered to detect the functionality, obfuscation techniques and vulnerabilities. Static analysis can also be used to extract artifacts from analysed malware such as files, C2 server addresses, settings etc. However, Static analysis does have its cons, it cannot provide details into the dynamic behaviour of malwares, and there is the possibility of static analysis to miss malicious activities that occur during runtime. It also cannot detect novel or sophisticated threats.</p><p><strong>BENEFITS AND LIMITATIONS OF DYNAMIC ANALYSIS</strong></p><p>Dynamic analysis provides insights into a malware behaviour like system interaction, file modification etc. The nature of Dynamic analysis also makes it detect malware that may escape static analysis by changing code or structure at runtime. It also provides real-time monitoring of malware behaviours. However, malware that use sandbox evasion technique are most likely to escape being detected by dynamic analysis. Also if not properly controlled and contained malware run in dynamic analysis can possibly contaminate the host system.</p><p><strong>DEFINING DEBUGGER, DISASSEMBLER AND DECOMPILER</strong></p><p>Debugging is the process of analysing, locating and correcting faults in a system. Debugging can be tedious because it involves understanding and monitoring the system to identify faults. Debuggers are used to learn the working process of malware and used to disable possible prevention mechanism. Disassemblers converts binary machine codes into human readable assembly language. Decompiler tool takes a program in form of executable file and produces high level language representation of that program.</p><p><strong>BEST PRACTICES FOR MALWARE ANALYSIS</strong></p><p>Analysis should be performed in an isolated environment to prevent the spreading of the malware, or if possible the analysis can be done offline to avoid network-based attacks. To prevent configuration or system files modification by malware, analysis environment should be boot from read-only media when possible, and regular snapshots should be taken so as to be able to revert to clean state. Industry recognized and reputable tools should also be used for the analysis and such tools should be well updated.</p><p><strong>STATIC ANALYSIS (PEStudio)</strong></p><p>PEStudio is a static analysis tool used to analyse files, it mainly analyse executable components on windows operating systems such as standard file formats for executables and dynamic link libraries.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1005/1*O9tJAf063JEq2Gy0k0O2Zg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/950/1*JRFg4lGSGniepg_WpQenmQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/954/1*wPoCYFuKJk_szHTH7i__lQ.png" /></figure><p>PEStudio tool was used to run a static anlysis on a malicious file, figure 11 above shows the basic file information ranging from signature, size, hex and others, also figure 11 shows the report of ViruTotal which is an online service that aggregates multiple antivirus engines to scan files, from the report it is obvious that the file analysed is malicious. Figure 12, also shows the imported functions from external DLLs. Figure 13, shows the strings imbedded in the file, we see strings like Get, Terminate, Ping which all have hidden actions.</p><p><strong>PROS AND CONS OF PEStudio</strong></p><p>PEStudio has a user friendly interface making it easy for user to navigate, PEStudio also extract and analyse strings that are found in a file making it easy to identify their functions and purpose in the executable file. DLLs that the executable file relies on are also being identified by PEStudio making it easy to understand their potential risks. However, PEStudio occasionally produces false positives flagging clean files as malicious, it also has the shortfall of not detecting complex malwares, it’s mainly useful in windows environment.</p><p><strong>DYNAMIC ANALYSIS (Procmon)</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/903/1*c7rt388vWocIICrKx9v9jw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/903/1*DiCcsT79p04Enz7eww8AZg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/903/1*EXlHraAlcVy_6lBkdqlLqg.png" /></figure><p>Figure 14, shows the start and end of the Bline malware file when been run a windows O.S, various processes were being triggered by the file. Figure 15, shows the command line and details of the malware start process while figure 16 shows that of the ping function of the malware file, which is pinging a certain Ip address.</p><p><strong>PROS AND CONS OF ProcMon</strong></p><p>Process Monitor, allows the user monitor activities, processes and thread operations in real-time because it captures wide range of system. It also provides detailed information that allows the user understand system activity and diagnose problems effectively. Its flexible filtering allows creation of complex filters and allows to focus on specific type of events. However, Procmon doesn’t allow for remote monitoring but rather only allows monitoring on local system, it also produce vast amount of information that might be too much for the user.</p><h3><strong>RECOMMENDATIONS</strong></h3><p>To further improve the security system of TSH, a mix of strategic and intentional security actions needs to be taken and put in place. This security actions need to be tailored to the organization’s requirement, the organization structure, the security system and the financial capabilities of TSH. The following recommendations are being suggested for TSH.</p><p>· Regular Staff Training: Majority of security breaches are as a result of human error, hence to prevent this TSH needs to regularly train their staff on security best practices, identification of social engineering attacks, spotting of phishing mails, password management and the likes.</p><p>· Use of Intrusion Detection System: IDS tools like Snort, Suricata, are used to detect malicious actions, it is important for TSH to pass their network traffic through IDS to detect if there is a traffic suitable for attacker behaviour. The administrator is quickly alerted when there is an abnormal behaviour.</p><p>· Use of Intrusion Prevention System: IPS is recommended for TSH because it is a more proactive security system that doesn’t only detect malicious activities but also takes actions to against those activities which can be possible security breach.</p><p>· Implementation of SIEM / SOAR: TSH should also include in their security system, Security Information and Event Management this enable TSH to collect, store, analyse and generate report of all their security events at a single location. This allows for central surveillance, threat detection and others. Also Security Orchestration and Response helps to streamline threat identification.</p><p>· Virtual Private Network: To maintain the CIA, TSH needs to implement a more secure remote access to the organization’s network, there is the need to have a strong encrypted connections to protect company data and network.</p><p>· Window Server Log Monitoring: TSH should also collect, store, analyse their web server logs and establish real-time monitoring to enable swift threat identification and ensure proper maintenance, tools like Elasticsearch and Kibana should be deployed.</p><p>· Central logging Monitoring: SSH security measures needs to be improved, to prevent unauthorized access and possible potential attacks and data breach.</p><p>· Other Possible Security Solutions: TSH can also look into onboarding more security solutions such as Endpoint detection and response, Data loss prevention, Email security solutions, Asset management solutions, web application firewall etc.</p><h3><strong>CONCLUSION</strong></h3><p>Implementing these security recommendations will help improve the security system of TSH and make is more resistant to unauthorized access and data breach.</p><p><strong>Disclaimer</strong><br>The names, organizations, and scenarios presented in this report are entirely fictional and are used solely for illustrative and educational purposes. TSH and the analyst identifier J111855 do not represent any real individuals or companies. Any resemblance to actual persons, living or dead, or actual entities, past or present, is purely coincidental.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=37bd631e88a4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[PENETRATION TESTING (EXPLOITATION, PRIVILEGE ESCALATION, RISK RATING & RECOMMENDATION)]]></title>
            <link>https://medium.com/@adeoyedavid55/penetration-testing-exploitation-privilege-escalation-risk-rating-recommendation-f94be731095d?source=rss-935cded74d48------2</link>
            <guid isPermaLink="false">https://medium.com/p/f94be731095d</guid>
            <dc:creator><![CDATA[Adeoye Iyanuoluwa David]]></dc:creator>
            <pubDate>Wed, 09 Jul 2025 18:49:07 GMT</pubDate>
            <atom:updated>2025-07-09T18:49:07.095Z</atom:updated>
            <content:encoded><![CDATA[<p>Penetration testing is a crucial part of any organization’s cybersecurity strategy. It involves simulating real-world attacks on an IT system to identify vulnerabilities before malicious actors can exploit them. The importance of penetration testing lies in its ability to identify vulnerabilities and how it can be exploited.</p><p>For every PenTest there has to be an actual exloitation, from my experience i have put up a sample of exploitations based on fictional characters</p><p>J111855 as Pentester</p><p>CEL as the Company.</p><p><strong>TOOLS USED</strong></p><p>Khali, Metasploit, Wire shark.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/728/1*WWYgOMY2t_Fbv_BlDxz9ug.jpeg" /></figure><p><strong>EXPLOITATION</strong></p><p>Listed below are some high severity vulnerabilities and the metasploit services/packages that can be used to exploit them;</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/619/1*z7iwcudkKSF7YC9YIHc_Gg.png" /></figure><p><strong>VSFTPD 2.3.4 Backdoor</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/930/1*a9FPod_1b6U5NDeJZcMj3A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/923/1*crHoQKnnkaYK0jeuwsYHjQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/637/1*Ty0s4CsJ8IMk5joA483Kdw.png" /></figure><p><strong>Java_rmi_server</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/937/1*bJpspCxqhmTDAsqKeP0kCw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/906/1*7phjQi5JKxiMJF0KT_EVOQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/641/1*jRYKvGPClzdDIDfoVT_iaA.png" /></figure><p><strong>PostgreSQL</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/911/1*PSOeM7Tj9wEpZr2dhoO8OQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/911/1*4BbxfddumwOTqXwzRe1NBA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*cfgkOn4W9vyzv3Eao9lzAQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/641/1*Rdbjj4fXNbF_8R-1JCWkhA.png" /></figure><p><strong>Php_cgi_arg_injection</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/906/1*NWiPl2x8stDYoZs-fi_HSA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/914/1*0Kr5Epw6hlEMGP-EYJYBOg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/907/1*CTYF5I2SA40LDDMLPy-BZg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/915/1*el_pslRkH6rZ64hOcmZIsg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/656/1*QLQ13aU5U9C6oBhKIcbAYA.png" /></figure><p><strong>APACHE DEFAULT CREDENTIALS</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/886/1*zNOOmb99gARsinvDbUoF_g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/878/1*I-JxtaORDmE-mbsFojdkOQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/627/1*8WN98dpvMyUaHJ9v1j4Kfw.png" /></figure><p><strong>Samba/usermap_script</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/933/1*UYmUUrVeGTycaXiIGpE51A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/623/1*zpvW3BC-aaOvc9MkRIWlJA.png" /></figure><p><strong>POST EXPLOITATION</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/902/1*QUYbso_e3MM7vTSXHrN_mw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/879/1*yfTG_3oInGgHBtyBs7EFNg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/627/1*lfklHVeNTcFQN7ATZH5eKA.png" /></figure><p>In addition at the <strong>post exploitation stage</strong>, when the attacker has successfully exploited the vulnerability and gained unauthorized root access to the system they aim to gain full control over the system and have <em>administrative privileges</em>. They also <em>pivot</em> through the network to further gain additional access to resources and more system increasing their compromise scope. They also sort to <em>escalate their privilege</em> to gain the highest level of access. Finally, they tend to want to <em>maintain their ongoing access</em> so they implement mechanism to gain control over the environment they have compromised.</p><h3><strong>RISK RATING</strong></h3><p>After assessing the available vulnerabilities and the potential outcomes and implication associated with exploitation them, J111855 consider CEL’s risk exposure to be HIGH, this is regarding possible malicious attack which can lead to breach, ransomware attack, data exfiltration which can all have varying implications on the business.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/595/1*QFL2h_1NF5A-9ZLPw2qBgA.png" /></figure><p><strong>CONCLUSION</strong></p><p>Based on the concluded Pentest assessment, the risk level in CEL across board is HIGH <em>table 16 &amp; 17.</em></p><p>System compromise was achieved and root access were gotten on exploited systems that contains sensitive data, if this exploitation is executed by an attacker it can put CEL at great financial and reputational risk that will significantly impact the business</p><p>System hardening needs to be done as means of <strong>technical</strong> <strong>countermeasures</strong> to help reduce the risk landscape of the organisation. Patch system management should be centrally managed to ensure all systems get regular security updates from vendors. Intrusion detection and prevention systems should be deployed to further strengthen the security posture. Firewall, honeypot and sandboxing. Access control should be introduced as <strong>policy countermeasures</strong> access policies should be designed around the principle of Least Privilege. However, while these security measures do have their own negative effects, it is important to note that organisations suffer financial loss as a result of weak security structure.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/632/1*0VreuFs-lkqYxCgpgzdVOg.png" /></figure><p>Overall, penetration testing is essential for proactively securing systems, minimizing risk, and maintaining a strong cybersecurity posture.</p><p><strong>Disclaimer</strong><br>The names, organizations, and scenarios presented in this report are entirely fictional and are used solely for illustrative and educational purposes. Chester Enterprise Ltd (CEL) and the analyst identifier J111855 do not represent any real individuals or companies. Any resemblance to actual persons, living or dead, or actual entities, past or present, is purely coincidental.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f94be731095d" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>