Unit 1: Information security concepts
Information Security notes · PTU syllabus (BSIT501)
On this page
- Unit summary
- Security overview and background
- Principles of security
- Information classification
- Policy framework
- Role-based security
- Components of an information system
- Balancing security and access
- Approaches to security implementation
- Security systems development life cycle
- Key terms
- Quick revision
- Important questions
Unit summary
Information security protects information and the systems that hold it. This unit covers the background of security, its principles, information classification, the policy framework, role-based security, the components of information systems, balancing security and access, approaches to implementation and the security systems development life cycle.
After this unit you can
- Explain the principles of information security
- Classify information and frame security policies
- Describe role-based security and components of an information system
- Explain implementation approaches and the SecSDLC
PTU syllabus topics
- Security overview and background
- principles of security
- information classification
- policy framework
- role-based security
- components of information systems
- balancing security and access
- security implementation approaches
- security systems development life cycle
Topic 1
Security overview and background
- Information security: protecting information and its critical elements — systems and hardware that use, store and transmit it — from unauthorised access, use, disclosure, disruption, modification or destruction.
- Background: early security was physical (guarding mainframes, 1960s); ARPANET in the 1970s raised network security issues; the 1990s internet boom, and later cloud, mobile and ransomware, made security a board-level concern. In India, the IT Act 2000, CERT-In and the Digital Personal Data Protection Act 2023 shape the framework.
Physical
Buildings, locks, guards
Personnel
Background checks, training
Operations
Procedures and continuity
Communications
Protecting media and messages
Network
Firewalls, IDS, VPN
Information
Data at rest and in transit
Example
Why security matters: a college stores student marks, fee payments and personal details. A single weak password can let an intruder change marks or steal data — damaging students, the college's reputation and its legal standing under data protection law.
Exam tip
Security protects information in three states: stored (at rest), moving (in transit) and being processed.
Topic 2
Principles of security
Confidentiality
Only authorised people can read — encryption, access control
Integrity
Data is accurate and unaltered — hashing, checksums
Availability
Systems and data accessible when needed — backups, redundancy, DDoS protection
Authentication, authorisation and non-repudiation
Verify identity, grant rights, prevent denial of actions — passwords, roles, digital signatures
- Other principles: accountability (actions traced through logs), least privilege, defence in depth, separation of duties, fail-safe defaults.
Example
One example for each principle: encrypting exam papers keeps them confidential; a checksum shows whether a downloaded file was altered (integrity); backup servers keep the college website running during a failure (availability); a digital signature stops a sender denying they sent a message (non-repudiation).
Exam tip
Learn the CIA triad first, then add authentication, authorisation and non-repudiation.
Topic 3
Information classification
- Top secret or restricted
Disclosure would cause grave damage — strategic plans, encryption keys
- Secret or confidential
Serious damage — customer data, salaries, exam papers
- Internal use only
Minor damage — internal circulars, phone lists
- Public
No damage — brochures, website content
- Process: identify information assets, assign an owner, classify by value and sensitivity, label, apply controls (encryption, access rights), and review periodically. Government uses top secret, secret, confidential, restricted; businesses use confidential, internal and public.
Example
Classifying college data: question papers before the exam are restricted; student marks and phone numbers are confidential; internal circulars are for internal use; the course list on the website is public. Each level gets different handling rules.
Exam tip
Higher classification = stricter access control, encryption and handling rules.
Topic 4
Policy framework
Enterprise information security policy (EISP)
Overall direction and scope, set by top management
Issue-specific policies (ISSP)
Email, internet use, BYOD, passwords
System-specific policies (SysSP)
Firewall rules, access control lists for a system
Standards, guidelines and procedures
Detailed mandatory rules, advice and step-by-step instructions
- Good policy: written, approved by management, communicated, understood and agreed by users, enforced uniformly and reviewed regularly.
Example
Three levels of policy: the college's enterprise policy says information must be protected; an issue-specific policy covers acceptable use of lab computers and Wi-Fi; a system-specific policy sets who can access the results database and with what rights.
Exam tip
Policies say what must be done; standards, procedures and guidelines say how.
Topic 5
Role-based security
- Role-based access control (RBAC): permissions are assigned to roles, and users are assigned to roles — a user gets exactly the rights needed for the job.
Discretionary (DAC)
Owner of the resource
File owner grants read access to a colleague
Mandatory (MAC)
System, based on labels and clearances
Military classified documents
Role-based (RBAC)
Administrator, by job role
Faculty role can enter marks; student role can only view
Attribute-based (ABAC)
Policies on user, resource and context attributes
Access only from the campus network during office hours
Example
College ERP roles: Admin (all modules), Accounts (fees), Faculty (attendance and marks), Student (view own records). When a teacher changes duties, only the role assignment changes.
Topic 6
Components of an information system
- Software
- Applications, operating systems, utilities — often vulnerable to bugs
- Hardware
- Computers and devices — can be stolen or damaged
- Data
- The most valuable asset and main target
- People
- Users and administrators — the weakest link through errors and social engineering
- Procedures
- Written instructions — leaked procedures help attackers
- Networks
- Connect systems and expose them to outside threats
Example
Every component can be attacked: stolen laptops (hardware), unpatched software, leaked database files (data), staff tricked by phishing (people), weak password-reset steps (procedures) and an open Wi-Fi network (networks).
Exam tip
Security must cover all six components, not just technology.
Topic 7
Balancing security and access
- Perfect security is impossible; security should be balanced against usability and cost.
Effect on users
Frustration, workarounds, lost productivity
Easy to use
Risk
Low but unusable
High exposure to attack
Example
Password change every week with 20 characters
Shared admin password for all staff
- Balance: risk assessment decides controls proportionate to asset value; multi-factor authentication and single sign-on improve both.
Example
Too much or too little: requiring a 20-character password changed every week makes staff write passwords on sticky notes, reducing security. Allowing no password at all makes access easy but unsafe. A strong password plus two-factor login balances both.
Exam tip
Security should be enough to protect assets without making systems unusable.
Topic 8
Approaches to security implementation
Initiated by
System administrators and technical staff
Senior management
Strengths
Technical expertise
Management support, budget, clear policy, accountability
Weaknesses
Lacks authority, funding and coordination
Needs champions and planning
Success rate
Low
High — preferred approach
Example
Top-down succeeds: when the principal approves a security policy, budget and training, every department follows it. When only the lab administrator tries to enforce rules (bottom-up), other departments ignore them for lack of authority.
Exam tip
Top-down has management support and is more likely to succeed.
Topic 9
Security systems development life cycle
- 1. Investigation: Management defines goals, scope and budget
- 2. Analysis: Study threats, existing controls, legal issues, risk
- 3. Logical design: Security blueprint, policies, continuity plans
- 4. Physical design: Select technologies, evaluate options
- 5. Implementation: Acquire, test, install, train
- 6. Maintenance and change: Monitor, test, update against new threats
Example
SecSDLC for a fee portal: investigation sets goals and budget; analysis studies threats like card fraud; logical design chooses controls; physical design selects specific firewalls and encryption; implementation installs and tests them; maintenance monitors and updates them.
Exam tip
Phases: investigation, analysis, logical design, physical design, implementation, maintenance and change.
Key terms
- Information security
- Protection of information and systems from harm
- CIA triad
- Confidentiality, integrity and availability
- Information classification
- Labelling information by sensitivity
- RBAC
- Access granted according to job role
- SecSDLC
- Life cycle for developing security systems
Quick revision
- Security history; layers of security.
- CIA, authentication, non-repudiation; least privilege, defence in depth.
- Classification levels; EISP, ISSP, SysSP.
- DAC, MAC, RBAC, ABAC; IS components.
- Security vs access; bottom-up vs top-down; SecSDLC phases.
Important exam questions
Practice questions written to the PTU exam pattern for this unit's syllabus: short answers (Section A style) and long answers (Sections B and C style).
Short-answer questions
- Q1.Define information security.
- Q2.State the CIA triad.
- Q3.What is information classification?
- Q4.Distinguish EISP and ISSP.
- Q5.What is role-based access control?
- Q6.Why is the top-down approach preferred?
Long-answer questions
- Q1.Explain the principles of information security.
- Q2.Explain information classification and the security policy framework.
- Q3.Explain role-based security and the components of an information system.
- Q4.Explain the security systems development life cycle.
Stuck on this unit?
Message SBS on WhatsApp for help with Information Security, or to ask about studying B.Sc IT at Synetic.
