- Definition
- Big Data Security refers to the tools, policies, and measures used to protect large volumes of data from unauthorized access, breaches, and misuse throughout its lifecycle — from collection to processing and storage.
- M2M (Machine to Machine)
- data exchanged between connected devices
- People to Machine
- data generated through human interactions with technology
- Organisational Data
- data produced by businesses and institutions
- Operational Big Data
- Operational Big Data refers to real or nearly real-time data used to support daily business operations and decision making. It processes data immediately as it is generated, supports transactional systems, and requires fast processing.
- Analytical Big Data
- Analytical Big Data refers to historical and accumulated data used for analysis, forecasting, reporting, and strategic decision making. It focuses on past and current data, supports business intelligence, and is often stored in data warehouses.
- Technical Skills
- programming, database management, big data frameworks
- Analytical Skills
- data analysis, pattern recognition, statistical analysis
- Business Skills
- translating insights into actionable business strategies
- Communication Skills
- presenting findings clearly to non-technical audiences
- Problem Solving Skills
- using data-driven approaches to solve complex problems
- Programming
- ability to write code to manipulate and process data
- Database Skills
- MySQL, Oracle — querying and managing structured data
- Big Data Frameworks
- Hadoop, Spark, Kafka — large-scale data processing tools
- Data sources
- Records the university already holds: semester results and GPA history per course, lecture attendance registers, student-portal login and activity logs, library borrowing and e-resource access, JAMB and O-level entry scores, departmental and level enrolment figures, fee-payment timing, and student feedback or…
- Collection and storage
- Most of this starts on paper or in departmental spreadsheets, so the first tasks are digitising it and agreeing one student identifier that works across departments. Structured records go into a central data warehouse; feedback text and portal logs suit a data lake.
- Type of analytics
- All four, in order. Descriptive answers what happened — pass rates by course and level. Diagnostic asks why — which factors track with failure. Predictive identifies which students are likely to carry over a course while there is still time to act. Prescriptive recommends which intervention to offer whom
- Tools and technology
- Python with pandas for the analysis, PostgreSQL or MySQL for the warehouse, and Power BI or Excel for dashboards that deans will actually open. Hadoop and Spark are the fashionable answer and the wrong one here: a single university produces gigabytes, not petabytes, and one relational database server handles that…
- Benefits and challenges
- Benefits: at-risk students identified before they carry over a course, better lecturer and timetable allocation, and evidence to support accreditation. Challenges: incomplete and inconsistent records, no single student identifier across departments, staff with no analytics training, unreliable power and connectivity…
- Volume
- Protecting petabytes or exabytes of data requires security tools that can scale dynamically without creating processing bottlenecks.
- Velocity
- Data streams into systems in real-time (e.g., IoT sensors, network logs). Security mechanisms like encryption and threat detection must happen on the fly without causing latency.
- Variety
- Big Data includes structured SQL databases, semi-structured JSON files, and unstructured data like video, audio, and text. A one-size-fits-all security policy does not work here.
- Encryption in Transit
- Protecting data as it moves between nodes, clusters, or users (typically using TLS/SSL).
- Encryption at Rest
- Safeguarding data stored on disks using strong encryption standards (like AES-256).
- Data Masking & Tokenization
- Replacing sensitive data (like credit card numbers or PII) with realistic but fake data or tokens before it enters the analytics pipeline so data scientists can work with it safely.
- Role-Based Access Control (RBAC)
- Assigning permissions based on organizational roles.
- Attribute-Based Access Control (ABAC)
- A finer-grained approach where access is determined by contextual attributes (e.g., "Allow access only if the user is a Data Analyst AND the request comes from an internal IP during working hours").
- Node Authentication
- Ensuring that only authorized servers/nodes can join the computing cluster (often managed via Kerberos).
The 26 topics define many more terms than these — the full set, with flashcards, is in the notes.