0% found this document useful (0 votes)
463 views3 pages

Incident Reporting Form: Form To Report Incidents To CERT-In

Download as pdf or txt
Download as pdf or txt
Download as pdf or txt
You are on page 1/ 3

Incident Reporting Form

Form to report Incidents to CERT-In

For official use only: Incident Tracking Number : CERTIn-xxxxxx

1. Contact Information for this Incident:


Name: Organization: Title:

Phone / Fax No: Mobile: Email:

Address:

2. Sector : (Please tick the appropriate choices)

Government Transportation Telecommunications InfoTech


Financial Manufacturing Academia Other ___________
Power Health Petroleum

3. Physical Location of Affected Computer/ Network and name of ISP.

4. Date and Time Incident Occurred:


Date: Time:
5. Is the affected system/network critical to the organization’s mission? (Yes / No). Details.

6. Information of Affected System:


IP Address: Computer/ Operating System (incl. Last Patched/ Hardware
Host Name: Ver./ release No.) Updated Vendor/ Model

7. Type of Incident:

Phishing Spam Website Intrusion


Network scanning /Probing Bot/Botnet Social Engineering
Break-in/Root Compromise Email Spoofing Technical Vulnerability
Virus/Malicious Code Denial of Service(DoS) IP Spoofing
Website Defacement Distributed Denial of Service(DDoS) Other_______________
System Misuse User Account Compromise

8. Description of Incident:
Incident Reporting Form

9. Unusual behavior/symptoms (Tick the symptoms)


Anomalies
System crashes Suspicious probes
New user accounts/ Accounting discrepancies Suspicious browsing
Failed or successful social engineering attempts New files
Unexplained, poor system performance Changes in file lengths or dates
Unaccounted for changes in the DNS tables, Attempts to write to system
router rules, or firewall rules Data modification or deletion
Unexplained elevation or use of privileges Denial of service
Operation of a program or sniffer device to Door knob rattling
capture network traffic; Unusual time of usage
An indicated last time of usage of a user account that Unusual usage patterns
does not correspond to the actual last time of usage Unusual log file entries
for that user Presence of new setuid or setgid files
A system alarm or similar indication from an Changes in system directories and files
intrusion detection tool Presence of cracking utilities
Altered home pages, which are usually the Activity during non-working hours or
intentional target for visibility, or other pages on holidays
the Web server Other (Please specify)

10. Has this problem been experienced earlier? If yes, details.

12. Agencies notified?


Law Enforcement Private Agency Affected Product Vendor Other_______________
11. When and How was the incident detected:

13. Additional Information: (Include any other details noticed, relevant to the Security Incident.)
Whether log being submitted Mode of submission:
OPTIONAL INFORMATION
14. IP Address of Apparent or Suspected Source:
Source IP address: Other information available:

15. Security Infrastructure in place:


Name OS Version/Release Last Patched/Updated
Name OS Version/Release
Last Patched / Updated
Anti-Virus
Intrusion Detection/Prevention
Systems
Security Auditing Tools
Secure Remote
Access/Authorization Tools
Access Control List

Packet Filtering/Firewall

Others
Incident Reporting Form

16. How Many Host(s) are Affected


1 to 10 10 to 100 More than 100
17. Actions taken to mitigate the intrusion/attack:
No action taken Log Files examined
Restored with a good backup
System Binaries checked System(s) disconnected form
Other___________________
network
Please fill all mandatory fields and try to provide optional details for early resolution of the
Security Incident
Mail/Fax this Form to: CERT-In, Electronics Niketan, CGO Complex, New Delhi 110003 Fax:+91-11-
24368546 or email at: incident@cert-in.org.in

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy