![200 OK” together with the requested page to the client,
otherwise it sends a corresponding error message, e.g.,
“HTTP/1.1 404 Not Found” or “HTTP/1.1 400 Bad Request”.
· If running the server program using command line, the syntax
should be:
server_code_name [<port_number>]
where the optional <port_number> is the port on which the
server is listening to connections from clients. If the port
number is not entered, the default port 8080 is used.
· You can test your Web server implementation on your local
machine using a Web browser, e.g., Internet Explorer, Firefox,
or Chrome. You need to specify the used port number within the
URL, for example,
http://localhost:8080/index.htm
If omitting the port number portion, i.e., 8080, the browser will
use the default port 80.
· The server should response with a default page when users do
not enter a specific page in the URL, for example,
http://localhost:8080/
It should also work when the request includes a path to the
requested file, for example,
http://localhost:8080/path/to/file/example.htm
· You should display/log the request and header lines of request
messages on the server for the purpose of debugging.
Requirements for the simple Web client
· The client is able to connect to the server via a socket and to
request a page on the server.
· Upon receipt of the response message from the server, the
client extracts and displays/logs the message status, and then
retrieves the page content from the message body.
· If running the client program using command line, the syntax
should be:
client_code_name <server_IPaddress/name> [<port_number>]
[<requested_file_name>]
where the <server_IPaddress/name> is the IP address or name of
the Web server, e.g., 127.0.0.1 or localhost for the server](https://image.slidesharecdn.com/projectpart3malwareprotectionprocedureguidescenarioal-221015120204-6920cd65/85/Project-Part-3-Malware-Protection-Procedure-GuideScenarioAl-docx-4-320.jpg)
Project Part 3 Malware Protection Procedure GuideScenarioAl.docx
- 1. Project Part 3: Malware Protection Procedure Guide Scenario Always Fresh allows external users, such as vendors and business partners, to access the Always Fresh Windows environment. You have noticed a marked increase in malware activity in the test environment that seems to originate from external users. After researching the likely source of new malware, you conclude that allowing external users to connect to your environment using compromised computers exposes Always Fresh to malware vulnerabilities. After consulting with your manager, you are asked to create a policy that will ensure all external computers that connect to Always Fresh environment are malware free. You create the following policy: “To protect the Always Fresh computing environment from the introduction of malware of any type from external sources, all external computers and devices must demonstrate that they are malware free prior to establishing a connection to any Always Fresh resource.” Consider the following questions: 1. What does “malware free” mean? 2. How can a user demonstrate that their computer or device is malware free? 3. What are the steps necessary to establish a malware-free computer or device? 4. How should Always Fresh verify that a client computer or device is compliant? Tasks
- 2. Create a malware protection procedure guide that includes steps for installing and running anti-malware software. Fill in the following details to develop your procedure guide: 1. Provide a list of approved anti-malware software solutions— include at least three leading antivirus and two anti-spyware products. You may include Microsoft products and third-party products. Instruct users to select one antivirus and one anti- spyware product and install them on their computer. 2. Describe the process of: a. Ensuring anti-malware software and data is up to date. Mandate daily updates. b. Running regular malware scans. Mandate that automatic scans occur whenever the computer is idle. If that setting is unavailable, mandate daily fast scans and biweekly complete scans. 3. Provide steps to follow any time malware is detected. a. Immediate reaction—what to do with current work, leave the computer on or turn it off b. Who to contact c. What information to collect The procedure guide may be used by company security professionals in the future. Hence, all steps listed should be clear and self-explanatory. Required Resources · Internet access · Course textbook Submission Requirements · Format: Microsoft Word (or compatible) · Font: Arial, size 12, double-space
- 3. · Citation Style: Follow your school’s preferred style guide · Length: 2 to 4 pages Self-Assessment Checklist · I created a procedure guide that provides clear instructions that anyone with a basic technical knowledge base can follow. · I created a well-developed and formatted procedure guide with proper grammar, spelling, and punctuation. · I followed the submission guidelines. Project 1 – CSE 4344 Building a Simple Web Client and a Multithreaded Web Server Objectives · To understand client-server communication via sockets. · To gain exposure to the basic operations of a Web server and client. · To explore basic structures of HTTP messages. Due: March 14, 2020 11:59pm Project Description In this project, you will be developing a multithreaded Web server and a simple web client. The Web server and Web client communicate using a text-based protocol called HTTP (Hypertext Transfer Protocol). Requirements for the Web server · The server is able to handle multiple requests concurrently. This means the implementation is multithreaded. In the main thread, the server listens to a specified port, e.g., 8080. Upon receiving an HTTP request, the server sets up a TCP connection to the requesting client and serves the request in a separate thread. After sending the response back to the client, it closes the connection. · The server is assumed to work with HTTP GET messages. If the requested file exists, the server responds with “HTTP/1.1
- 4. 200 OK” together with the requested page to the client, otherwise it sends a corresponding error message, e.g., “HTTP/1.1 404 Not Found” or “HTTP/1.1 400 Bad Request”. · If running the server program using command line, the syntax should be: server_code_name [<port_number>] where the optional <port_number> is the port on which the server is listening to connections from clients. If the port number is not entered, the default port 8080 is used. · You can test your Web server implementation on your local machine using a Web browser, e.g., Internet Explorer, Firefox, or Chrome. You need to specify the used port number within the URL, for example, http://localhost:8080/index.htm If omitting the port number portion, i.e., 8080, the browser will use the default port 80. · The server should response with a default page when users do not enter a specific page in the URL, for example, http://localhost:8080/ It should also work when the request includes a path to the requested file, for example, http://localhost:8080/path/to/file/example.htm · You should display/log the request and header lines of request messages on the server for the purpose of debugging. Requirements for the simple Web client · The client is able to connect to the server via a socket and to request a page on the server. · Upon receipt of the response message from the server, the client extracts and displays/logs the message status, and then retrieves the page content from the message body. · If running the client program using command line, the syntax should be: client_code_name <server_IPaddress/name> [<port_number>] [<requested_file_name>] where the <server_IPaddress/name> is the IP address or name of the Web server, e.g., 127.0.0.1 or localhost for the server
- 5. running on the local machine. The optional <port_number> is the port on which the server is listening to connections from clients. If the port number is not entered, the default port 8080 is used. The optional <requested_file_name> is the name of the requested file, which may include the path to the file. If the file name is not entered, the default file “index.htm” is used. Notes: · This is an individual project. · You can use the programming language of your choice. (You may get more help with Java or Python.) · You may use the skeleton code for the server provided in the textbook’s companion website for reference. You may also want to refer to the textbook, chapter 2, section 2.2.3, for more details on HTTP message format and section 2.7, for socket programming. · The source codes should be well documented to make it easier for the TA to follow. Submission Guidelines · Submit a single zipped file with the naming convention <your_UTA_id>_<your_name>.zip which consists of: · Source codes of the Web server and client, · Any additional files required to run your codes, · A readme file with instructions on how to compile and run your codes. You must mention the IDE as well as any packages that are required to run the codes. · Do NOT include any runnable executable (binary) program. · Make sure your name and your UTA ID are also listed in the readme file and in comments at the beginning of your source files. · Upload the zipped file via Canvas. Please strictly follow the naming convention of the zipped file and the subject title. · Late submission will be accepted with a 10-point deduction for each extra day. Additional Requirements/Instructions · Complete documentation and instructions for running the codes are recommended, otherwise you may be asked to come
- 6. give the TA a demo if he is not able to run your programs from the instructions provided. · If you are using any code from some external source or book, you MUST mention it explicitly in the codes as well as the readme file. Otherwise, it will be considered plagiarism and your project will not be evaluated. · You can discuss with other classmates on steps/algorithms to implement the project. However, the source codes must be written yourself. Grading (100 points) · The server works correctly with requests from a Web browser (20 points) · The server can serve multiple requests at the same time (multithreaded implementation) (20 points) · The client sends/receives messages to/from the server correctly (20 points) · The client extracts the status and content of messages from the server correctly (20 points) · Display/log of proper messages on the server (5 points) · Display/log of proper messages on the client (5 points) · Code documentation (5 points) · Readme file (5 points) · Late submission: 10-point deduction for each extra day.