CIS2026-N Ethical Hacking

Java Python CIS2026-N

Ethical Hacking

Scenario

A  not-for-profit  organisation  working  on  human  rights  protection  ask  you  to  plan,  execute  and document an ethical hack against their systems to assess their security. Moreover, based on your findings, you are required to provide advice on how to improve the security of the system.

The  organization   periodically  receives  reports  from  whistle-blowers  and   independent  advisors regarding alleged systematic violations of human rights in different countries. These reports could constitute support documentation for actions taken by the organisation such as legal action against alleged offenders or media campaigns.

The organisation is concerned that a possible data breaches that may compromise the confidentiality of the information and the identity of whistle-blowers and advisors.

For your security analysis, they provide you the following scheme and details:

A Linux based firewall/router controls the access to different zones of the system (zones are separate network entities, with no traffic across zones allowed without special permission):

Red — the Internet

Green — the safe zone for maximum protection

Orange — a DMZ designed for Web, mail, or other Internet servers Blue — for wireless networks

Orange Zone:

The webserver is an Ubuntu 20.04 LTS machine running Apache 2.4.x

The email server is a MS Windows Server 2019 Standard, running MailEnable Standard Edition 10.41

Green Zone:

The Server: Windows Server 2019, with Active Directory, DHCP, DNS, IIS. The server also run a MySQL Server 8.0.30, the back end for a custom web application that is used by the admin and financial office. The server contains also shared folders, which are  used for  different  purposes:  projects,

advisors reports, and other classified and non-classified documents The workstations are Windows 10 21H2 machines.

Blue Zone:

Employees and volunteers are allowed to bring their own device and connect to the Internet.

No further information and no credentials are given except the public IP address and the domain name  of  the  web   server  (since  this   information  is  purely  hypothetical,  we  simply   use  these placeholders and to indicate them in your report).

Client requirements

The client specifically requests that:

-     No data should be lost from any system during the pen testing. If any change is done, for a proof-of-concept, you should also identify a procedure to restore the system to the previous state, provided the pen-tester has double checked with client that a back up exists and it is safely stored.

-     The risk of disrupting the services should be minimised during office hours.

-     You have a limited number of hours for this task, so your planning should prioritise the key services and components.

-     The pen testing activities should be carried out with FOSS or free software unless such option does not exist for a specific task. In this case, you should make clear the licence terms and costs.

Task

You should write a report (approximately 4500 words, submitted in PDF format) detailing your plan, with a justification for tools and techniques used, the results and a complete chronological audit trail of hacking actions taken in line with expected professional and ethical standards.

For the practical part, you must carryout a pen testing limited to a given virtual machine (information about location of the virtual machine is available on Blackboard, under “Assessment”). For the rest of the work, use the information provided in the scenario, and make the appropriate and reasonable assumptions if necessary (provide a rationale for it).

The report will have to cover all the stages of the ethical hacking methodology. The report should include at least the following elements (xx% indicates the weight in the mark allocation):

1.          Demonstration of understanding of the scenario and discussion of the pre-engagement interactions. (10%)

2.          Identification of relevant tools for each stage of the ethical hacking. (10%)

3.          Appropriate information gathering and threat modelling (10%)

4.          Identification of security vulnerabilities (10%)

5.          Exploitation of the vulnerabilities (10%)

6.          Post exploitation activities (10%)

7.          Reporting of the findings and potential suggestions for countermeasures (10%)

8.          Critical reflection of self-performance and the development of skills for employment as a computer security professional. (10%)

The remaining 20% of the final grade is allocated  based on the overall quality of the  report: formatting, completeness, readability, and appropriate referencing.

Elements 4, 5, 6, 7 are relevant for the practical part (as you must report the analysis of the given component) and the results of such activities should be documented and explained, also using appropriate screenshots.

For the element 7 you should also include countermeasures and recommendations deduced from the  scenario,  but  they  should  be  clearly  separated  from  ones  deduced  from  the  practical elements.

N.B. The component provided for the practical part is not depicted in the diagram, but you can assume it is in the Orange zone and you have direct access to it.

Students will be assessed on the following learning outcomes:

1.   Communicate effectively and professionally to report on system security.

2.   Create and maintain an audit trail of all process undertaken during an ethical hack.

3.   Apply tools and techniques in a structured, ethical, and professional manner to evaluate system security using ethical hacking methodologies.

4.   Demonstrate knowledge of appropriate security analysis techniques, common vulnerabilities, and countermeasures.

5.   Identify the professional, ethical, and legal issues associated with ethical hacking.

6.   Operate ethically and within professional guidelines whilst conducting security testing.

Marking Criteria

Marks are provided as a guidance

A/A+/A++

75%/85%/95%

Excellent

An excellent answer demonstrating informed judgements about the

task/scenario. Appropriate measures are selected and justified clearly. Autonomy of investigation is shown.

Demonstrated excellent consideration of relevant professional, legal and ethical issues with very good linkage to the scenario/task.

A very clear and readable report, with excellent structuring, good use of grammar and referencing. Document submitted as PDF.

An excellent completion of the practical elements.

B

65%

Substantially correct/appropriate (based on taught material & module requirements)

A good answer demonstrating informed judgements about the task/scenario. Appropriate measures are selected and justified. Autonomy of investigation is shown.

Demonstrated appropriate consideration of relevant professional, legal and ethical issues in relation to the scenario/task.

A clear and readable report, with appropriate structuring and referencing. Document submitted as PDF.

A good completion of the practical elements.

C

55%

Minor errors/omissions/issues

A mostly good answer with only minor errors/omissions/issues. The answer demonstrates informed judgements about the task/scenario. Appropriate measures are selected and justified. Some autonomy of investigation is shown.

Demonstrated fairly appropriate consideration of relevant professional, legal and ethical issues in relation to the scenario/task with only minor errors/omissions/issues.

A clear and readable report, with minor errors in writing, structure or referencing. Document submitted as PDF.

A fairly good completion of the practical elements.

D

45%

Major errors/omissions/issues

A limited answer with major errors/omissions/issues. The answer demonstrates some informed judgements about the task/scenario. Some appropriate measures are selected and justified. Limited

autonomy of investigation is shown.

Demonstrated some consideration of relevant professional, legal and

ethical issues in relation to the scenario/task with major errors/omissions/issues.

A report, with major issues of writing, structure or referencing. Document submitted as PDF.

A sufficient completion of the practical elements

E

35%

Unsatisfactory

A very limited answer. The answer demonstrates some few judgements about the task/scenario. Few measures are selected and justified. Little autonomy of investigation is shown.

Little consideration of relevant professional, legal and ethical issues in relation to the scenario/task.

A report that is difficult to reador comprehend but includes some

attempt at structure and referencing OR document is not submitted as a PDF.

An insufficient attempt to complete the practical part.

F

0%-20%

Inadequate

The answer barely addresses the task/scenario, if at all.

Little to no consideration of professional, legal, and ethical issues.

A report that is very difficult to read and comprehend and makes no attempt at referencing.

Noor very limited attempt to complete the practical elements         

基于51单片机,实现对直流电机的调速、测速以及正反转控制。项目包含完整的仿真文件、源程序、原理图和PCB设计文件,适合学习和实践51单片机在电机控制方面的应用。 功能特点 调速控制:通过按键调整PWM占空比,实现电机的速度调节。 测速功能:采用霍尔传感器非接触式测速,实时显示电机转速。 正反转控制:通过按键切换电机的正转和反转状态。 LCD显示:使用LCD1602液晶显示屏,显示当前的转速和PWM占空比。 硬件组成 主控制器:STC89C51/52单片机(与AT89S51/52、AT89C51/52通用)。 测速传感器:霍尔传感器,用于非接触式测速。 显示模块:LCD1602液晶显示屏,显示转速和占空比。 电机驱动:采用双H桥电路,控制电机的正反转和调速。 软件设计 编程语言:C语言开发环境:Keil uVision。 仿真工具:Proteus。 使用说明 液晶屏显示: 第一行显示电机转速(单位:转/分)。 第二行显示PWM占空比(0~100%)。 按键功能: 1键:加速键,短按占空比加1,长按连续加。 2键:减速键,短按占空比减1,长按连续减。 3键:反转切换键,按下后电机反转。 4键:正转切换键,按下后电机正转。 5键:开始暂停键,按一下开始,再按一下暂停。 注意事项 磁铁和霍尔元件的距离应保持在2mm左右,过近可能会在电机转动时碰到霍尔元件,过远则可能导致霍尔元件无法检测到磁铁。 资源文件 仿真文件:Proteus仿真文件,用于模拟电机控制系统的运行。 源程序:Keil uVision项目文件,包含完整的C语言源代码。 原理图:电路设计原理图,详细展示了各模块的连接方式。 PCB设计:PCB布局文件,可用于实际电路板的制作。
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
红包 添加红包
表情包 插入表情
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值