Lecture 5 - Endpoints and Application Development Security
Lecture 5 - Endpoints and Application Development Security
Organizations are now pooling resources and knowledge about the latest attacks with the
broader security community
One type of shared information is the evidence of an attack
Key risk indicators (KRIs) are metrics of the upper and lower bounds of specific indicators
of normal network activity
These indicators may include the total network logs per second, number of failed remote logins,
network bandwidth, and outbound email traffic
A KRI exceeding its normal bounds could be an indicator of compromise (IOC)
An IOC shows that a malicious activity is occurring but is still in the early stages of an attack
IOC information aids others in their predictive analysis or discovering an attack before it occurs
Categories of Sources (1 of 3)
Two categories of threat intelligence sources are open source and closed source
Open Source Information
“open source” refers to anything that could be freely used without restrictions
Open source threat intelligence information is often called open source intelligence (OSINT)
Cyber Information Sharing and Collaboration Program (CISCP) enables actionable, relevant, and
timely unclassified information exchange through partnerships
CISP services include:
Analyst-to-analyst technical exchanges
CISCP analytical products
Cross industry orchestration
Digital malware analysis
Categories of Sources (2 of 3)
Ensuring secure startup involves the Unified Extensible Firmware Interface (UEFI) and its
boot security features
Unified Extensible Firmware Interface (UEFI)
Early booting processes used firmware called the BIOS (Basic Input/Output System)
To add functionality, an improved firmware interface was developed to replace BIOS
UEFI includes:
The ability to access hard drives that are larger than 2TB
Support for an unlimited number of primary hard drive partitions
Faster booting
Support for networking functionality in the UEFI firmware itself to aid in troubleshooting
Confirm Boot Integrity (2 of 3)
Confirm Boot Integrity (3 of 3)
Boot Security
The ability to update the BIOS in firmware opened the door for a threat actor to create malware
to infect the BIOS (called a BIOS attack)
Boot security involves validating that each element used in each step of the boot process has not
been modified
This process begins with validation of the boot software, then it can validate the software drivers,
and so on until control has been handed over to the OS
Called chain of trust because each element relies on the confirmation of the previous element to know
that the entire process is secure
The strongest starting point is hardware, which cannot be modified like software (known as hardware
root of trust)
Protect Endpoints (1 of 4)
Antimalware
Antimalware is a suite of software intended to provide protections against multiple
types of malware
Antimalware spam protection is often performed using a technique called Bayesian
filtering
Filters by analyzing every word in each email and determines how frequently a word
occurs in a spam pile versus a nonspam pile
Another component of an antimalware suite is antispyware, which helps prevent
computers from becoming infected by spyware
Uses pop-up blockers, which allow the user to select the level of blocking, ranging from
blocking all pop-ups to allowing specific pop-ups
Protect Endpoints (3 of 4)
Web Browsers
Webbrowsers offer the following security on endpoint
computers:
Secure cookies are sent to a web server with an encrypted request
over the secure HTTPS protocol
This prevents an unauthorized person from intercepting a cookie that is
being transmitted between the browser and the web server
HTTP Response Header are headers that tell the browser how to
behave while communicating with the website
Protect Endpoints (4 of 4)
Operating Systems
Securing an OS involves proper security configurations and using confinement tools
A typical OS security configuration should include the following:
Disabling unnecessary ports and services
Disabling default accounts/passwords
Employing least functionality
In Microsoft Windows, a security template is a collection of security configuration settings that can be
used to deploy security settings to multiple computers
Windows 10 Tamper Protection security feature prevents Windows security settings from being
changed or disabled by a threat actor who modifies the registry
A Group Policy setting can also prevent access to registry editing tools (see Figure 4-7)
Harden Endpoints (3 of 6)
Operating Systems (continued)
Harden
Confinement Tools – several tools
Endpoints can be used to restrict malware:
Application whitelisting/blacklisting
(4 of 6) Sandbox
Quarantine
Harden Endpoints (5 of 6)
Harden Endpoints (6 of 6)
Creating and Deploying SecDevOps (1 of 2)
An unsecure application can open the door for attackers to exploit the application, the
data that it uses, and even the underlying OS
A directory traversal attack takes advantage of vulnerability in the web application
program or the web server software so that a user can move from the root directory to
other restricted directories
The ability to move could allow an unauthorized users to view confidential files or
enter commands to execute on a server known as command injection
Other dangerous weaknesses in an application can create vulnerabilities in computer
memory or buffer areas that can be easily exploited
Poor memory management vulnerabilities result in attacks such as buffer overflow,
integer overflow, pointer/object deference, and DLL injection attacks
Creating and
Deploying
SecDevOps
(2 of 2)
Application Development Concepts (1 of 3)
The two levels of application development concepts include general concepts that apply to all
application development and those that apply to a rigorous security-based approach
General Concepts
Developing an application requires completing the following stages:
Development
Testing
Staging
Production
Software diversity is a software development technique in which two or more functionally identical
variants of a program are developed from the same specification but by different programmers or
programming teams
The intent is to provide error detection, increased reliability, and additional documentation
Application Development Concepts (2 of 3)
SecDevOps (continued)
SecDevOps is the process of integrating secure development best practices and methodologies
into application software development and deployment processes using the agile model
SecDevOps applies automated courses of action to develop code as quickly and securely as
possible
This automation enables:
Continuous monitoring
Continuous validation
Continuous integration
Continuous delivery
Continuous deployment
Secure Coding Techniques
Organizations are pooling their experiences and knowledge gained about the latest attacks with
the broader security community because sharing this type of information has become an
important aid to help other organizations shore up their defenses
Several sources of threat intelligence are useful: a vulnerability database, a cybersecurity threat
map, and file and code repositories are examples
One of the steps that is often overlooked in securing endpoint computers is to confirm that the
computer has started without any malicious activity taking place
Antivirus (AV) software can examine a computer for any file-based virus infections and
monitor computer activity and scan new documents that might contain a virus
Web browsers have a degree of security that can protect endpoint computers
A host intrusion detection system (HIDS) is a software-based application that runs on an
endpoint computer and can detect that an attack has occurred
Summary (2 of 2)
One of the most important steps in securing an endpoint computer is to promptly install
patches
An unsecure application can open the door for attackers to exploit the application, the data
that it uses, and even the underlying OS
Testing is one of the most important steps in SecDevOps
References
Ukeje, N., Gutierrez, J., & Petrova, K. (2024). Information security and privacy challenges of
cloud computing for government adoption: a systematic review. International Journal of
Information Security, 1-17.
Ali, A. S., Zaaba, Z. F., & Singh, M. M. (2024). The rise of “security and privacy”:
bibliometric analysis of computer privacy research. International Journal of Information
Security, 23(2), 863-885.
Farayola, O. A., Olorunfemi, O. L., & Shoetan, P. O. (2024). Data privacy and security in IT: a
review of techniques and challenges. Computer Science & IT Research Journal, 5(3), 606-615.