2incident Management
2incident Management
Cybersecurity Bureau-CERT-PH
WHOAMI: ALWELL MULSID
• Bachelor Degree in Computer Information Science
• L e a d t h e I n c i d e n t R e s p o n s e S e c t i o n o f C E R T- P H ,
DICT
• Alumnus of
- Japan International Cooperation Agency (JICA) in Japan
-J a k a r t a Cent re For Law Enforcement Cooperat ion(JC LEC) in
Indonesia
-I n t e r n a t i o n a l V i s i to r L e a d e rs h i p P rog ra m ( IV LP ) by US
State Department
• The methodology can effectively identify, minimize the damage, and reduce
the cost of a cyber attack, while finding and fixing the cause to prevent
future attacks.
Goal of Incident Response (IR)
It will help your organization to ensure that your team can act before, during and
after a cyber attacks.
Incident Response Lifecycle
1. Preparation
• Preparedness Program
• Policies and security documents
• Create the Incident Response Team
• Understand your organization’s operations and business environment;
• Identification and inventory of the assets that need to be protected and
prioritized;
• Establish systems for recording, monitoring and ticketing of incidents
• The use of equipment and technology to detect and address a cyber security
incident;
Incident Response Lifecycle
1. Preparation
• Outline the roles, responsibilities, and procedures of your team
• Incident response kit and tools
• Establish clear communication channels
• Telecommuting
• In-house capabilities or contracts with external experts for incident response
and/or forensic investigation in case of an actual cyber security incident;
• Develop common incident playbooks
Incident Response Lifecycle
2. Detection and Analysis
Detect and analyze events in order to determine if these events are considered
security incidents. It requires to use tools, systems and skills of incident response
personnel in monitoring and identifying any unusual activity or events that may
compromise the confidentiality, integrity and availability of the organization
information and systems.
Incident Response Lifecycle
2. Detection and Analysis
Focus on : Unusual Activities and Events
• Alerts and reports about potential malicious activity or vulnerabilities. This
can include alerts from your technology or network provider.
• loss or breach of a device, including personal mobiles that staff use to access
work emails. Staff may feel uncomfortable about reporting such incidents so
it's important to encourage people to speak up proactively.
• General day-to-day indicators, such as unusual email activity, incident reports, or being
informed by staff or customers that a breach has already occurred.
Incident Response Lifecycle
2. Detection and Analysis
Focus on : Detection Methods
• Detected by security controls
(Intrusion Detection System, Firewall)
• Monitored by security personnel
(Internal IT, SOC , CERTs using tools)
• Reported by end-users / Victims
(Traditional anti-virus, anti-malware, computer users and victims)
• Detected by external security teams and Researchers
• (Dark web, specialized search engine, social media, vendors, other CERTs)
Incident Response Lifecycle
3.1. Containment
The goal is to check the affected system or digital assets and to limit the damage
from the current incident. It is also important to prevent the destruction of
evidence that may be needed for legal proceedings.
Incident Response Lifecycle
1. Containment
Focus on : Applying different strategies
• Removing the system from the network by disconnecting it
• Isolating the systems by way of network segmentation
• Utilize virtual local area network
• Utilize firewall rule sets
• Monitoring the attacker communication channels and activities on the
system
• Carefully gathering of information and evidences for legal proceedings
• Redirecting Traffic
• Whitelisting of IPs to boot out attackers
Incident Response Lifecycle
1. Containment
• Focus on : Documentation / Management Decision / Other activities
• Approval in accessing the victim machines and related applications. Possibly
stores sensitive data
• Ensures contaminated machines and equipment is protected from
unauthorized access by non-incident responder or owner of the system
• Communications to IR lead and higher ups is necessary so that they are well
informed and can come up with decisions.
Incident Response Lifecycle
3.2. Eradication
Involves the process of understanding the cause of the incident for the affected
entity to be able to reliably recover from the incident by removing the malicious
files or other artifacts included in the attacks.
Incident Response Lifecycle
2. Eradication
• Wipe out content and re-image of affected system hard drives to ensure any
malicious content is removed.
• Preventing the root cause - understanding what caused the incident
preventing future compromise, for example by patching a vulnerability
exploited by the attacker.
• Applying basic security best practices—for example, upgrading old software
versions and disabling unused services.
Malicious USB / Other Use of tools such as IR team can use the
External HDD autopsy, imager and device to do digital
other tools available forensics and analysis
on the content of the
device.
Habits of ….
• changing the default passwords
• thinking twice before clicking unknown links or
opening email from unknown senders
• allowing a week without updating your backup
Cybersecurity Habits for Incident Responders
Habits of ….
• verifying request of your private information.
• not to use work computers for personal activities
• securing your area and locking your computer screen
before leaving them unattended – even just for a
second
Cybersecurity Habits for Incident Responders
Habits of ….
• not using company email address in registering to
non-office related websites and services.
• using passwords for different social media account
THANK YOU
alwell.mulsid@dict.gov.ph
https://www.ncert.gov.ph
https://www.facebook.com/ncertgovph