liveBook · Manning

Malicious code

Malicious code is software or executable content intentionally designed to perform unauthorized, harmful, disruptive, deceptive, or security-compromising actions.

How 3 Manning books explain it

Acing the CCNA Exam: Volume 2 Advanced Networking and Security

Malware is software designed to perform malicious actions or compromise the confidentiality, integrity, or availability of systems or data.

How it is used
Positions malware as a technical threat and connects it to attacks affecting confidentiality, integrity, or availability.
How deep it goes
Defines malware as harmful software that infects targets and performs malicious actions, then connects it to botnets and DDoS.
Examples
Uses malware-infected botnets and TCP SYN floods to illustrate distributed denial-of-service attacks.
What you can do after
Evaluate malware’s role in technical threats and recognize its connection to botnets and distributed denial-of-service.

Read how Acing the CCNA Exam: Volume 2 Advanced Networking and Security explains malicious code →

AI for Everyday IT

Malware is software intentionally designed to damage systems, disrupt operations, or gain unauthorized access to data or resources.

How it is used
Uses email inspection and AI analysis to identify phishing routes for malicious code and protect organizational data.
How deep it goes
Defines malicious code briefly, then demonstrates phishing analysis through email headers, source text, and authentication failures.
Examples
Uses suspicious emails, Outlook headers, pasted source text, M365 Copilot, SPF failures, and DKIM failures.
What you can do after
Diagnose suspicious emails by examining headers and source text with an AI service before opening links or sharing information.

Read how AI for Everyday IT explains malicious code →

Grokking Web Application Security

Malicious code is program code intended to perform unauthorized, harmful, or security-compromising actions.

How it is used
Frames injection risks as ways attackers make web servers run harmful code or instructions.
How deep it goes
Explains attack consequences and defensive input handling, while deferring difficult malicious-file-content validation.
Examples
Uses ransomware deployment and MIME-type checking of an uploaded image as concrete examples.
What you can do after
Apply it via server-side validation, cautious upload handling, and isolation of stored files from application servers.

Read how Grokking Web Application Security explains malicious code →

Related concepts

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.