Cybersecurity (up to class 14)

0.0(0)
studied byStudied by 0 people
0.0(0)
full-widthCall Kai
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
GameKnowt Play
Card Sorting

1/74

flashcard set

Earn XP

Description and Tags

Interview Questions and Terms ; up till policies

Study Analytics
Name
Mastery
Learn
Test
Matching
Spaced

No study sessions yet.

75 Terms

1
New cards

IAM

Identity and Access Management. Process of onboarding and offboarding people

2
New cards

Cyber Threat

Any malicious act that attempts to gain access to a computer network without authorization. Can damage or disrupt computer system, a network of the information it contains

  • Most Common Cyber Threats: Social Engineered Trojans, Unpatched Software, Phishing, Network worms

3
New cards

Cyber Attacks

Advanced Persistent Threat (APT), Backdoor, Cross0Site Scripting, Zero-day Exploit, Impacts and Malicious Code

4
New cards

What is a vulnerability?

 A vulnerability is the composition of three elements:

  • A flaw in the system.

  • Access to the attacker to that flaw.

  • The capability of the attacker to exploit the flaw.

5
New cards

SDLC

Software Development Life Cycle. The process for developing a software application or system

6
New cards

SDLC Phases

  • Planning

    • Customer needs -> budget, resources, timeline

  • Defining/Analysis

    • Requirements defined by BA

  • Design

    • Blueprint developed by System Architect

    • Servers, Databases, Integrations

  • Coding/Developing

  • Testing 

  • Deployment/Production

7
New cards

Agile

Methodology to move quickly and easily; a formalized approach for delivering SDLC 

8
New cards

Backlog

List of requirements that need to be delivered

Product Backlog, Spring Backlog, Release Backlog

9
New cards

User Stories

Business Needs, core values of expectations and acceptance criteria. Analyzed by testing SMART

10
New cards

Requirements

Customer Needs written in a detailed and technical format

11
New cards

Functional Requirements

Describes what the system SHOULD do

User Action → System Reaction

12
New cards

Non-Functional Requirements

Describes how the system should work

  • Majority of Requirements IAMs work with

  • Set up triggers, rules in system

  • Performance, Availability and Security (Giving access and removing access)

13
New cards

SQL

Organizes back-end data

14
New cards

Data Definition Language

DR CAT

  • DROP - delete object (table or database) from the database

  • RENAME - rename the existing table or object

  • CREATE - to create table or objects

  • ALTER - change the structure (name, data type)

  • TRUNCATE - remove all records from a table

15
New cards

Data Manipulation Language

  • SELECT - extract data

  • UPDATE - update data

  • DELETE - delete data (can delete a record)

  • INSERT - insert new data 

16
New cards

Transactional Control Language

  • COMMIT - save the data

  • ROLLBACK - undo

17
New cards

Data Control Language

  • Giving access to specific users

  • GRANT - assign privilege

  • REVOKED - remove privilege

18
New cards

API

Application Program Interface

Middle Tier that checks valid responses between front end (client) and back end (server) in an application

19
New cards

API Testing

Sending Calls

20
New cards

Web Service

A service available over the web

  • API wrapped in HTTP

  • Needs a network while an API doesn’t need a network

21
New cards

SOAP (Simple Object Access Protocol)

Web Service API that uses SoapUI (Manual Testing)

Uses tags like HTML

Send data through Auto Populated header instructions

22
New cards

RESTful

Web Service API that uses Postman for Manual Testing and REST-assured for Automation Testing

Most are JSON

The server will transfer the client a representation of the state of the requested resource

23
New cards

WSDL

Web Services Description Language

XML based language that describes Web services and how to access and locate them

24
New cards

UDDI

Universal Description, Discovery and Integration

Open internet based specification that offers directory service for storing information about web services

25
New cards

SOAP Vs REST APIs

  • SOAP is like using an envelope, extra overhead, more bandwidth requested, more work on both ends.

  • REST is like a postcard: lightweight, can be cached, and easier to update. Not as private. 

26
New cards

Network Security

Focuses on protecting roads (cisco, vpn)

27
New cards

Endpoint Security

Protects individual devices (antivirus, encryption)

28
New cards

Application Security

Apps are secure during development & use (regular app testing)

29
New cards

Data Security

Secure systems hosted in cloud (AWS Security Hub ; cloud encryption)

30
New cards

Identity

Unique digital representation of a person, device, application, etc

31
New cards

User

Who has an account in identity management

32
New cards

Administrator

Has the capability and controls organization

33
New cards

Resources

Systems, applications, or data that a user may need access to

34
New cards

Organization

The structure users/identities belong to (teams or locations)

35
New cards

Role

A set of permissions a user gets based on their job functions. Bundle of entitlements someone is assigned to based on their role

36
New cards

Capabilities

Actions or tasks an identity is allowed to perform

37
New cards

Virtual Identity

How a user looks in Sailpoint

38
New cards

SOD policy

separation of duties; 2 conflicting roles setting the policy by going into sailpoint instance by marking what role conflicts

39
New cards

Application Server

Where Sailpoint is going to run; Tomcat

40
New cards

Database Server

Sailpoint’s data ; Shared access for everyone to view ; MySQL

41
New cards

Java

Development written in java beanshell (rules, scripts) BEANSHELL IS XML AND JAVA CODE (getters: objects, identities & setters: firstname, email)

42
New cards

Sailpoint WAR

Sailpoint file you’ll be able to run on servers

43
New cards

UI Server

lets sailpoint be up and running

44
New cards

Task Server

tasks you can run (ex. updating identities); might need multiple servers depending on how many identities you have, making sure everyone can do their tasks and also need backup

45
New cards

Load Balancer

directs traffic to different servers to avoid request overload

46
New cards

Hibernate

communicate with the database

47
New cards

Entitlement

permission / acess right

48
New cards

Certification / User Access Review

When managers go in and review accesses that users would need, revoke what is not needed

49
New cards

Policy

Rules in Sailpoint

50
New cards

Attributes

datapoints used to describe an identity

51
New cards

Aggregation

pulling data from connected applications; sailpoint uses connector to go through identities then pulls them into Sailpoint

52
New cards

Account mapping

Part of Aggregation

link user identities within all different applications; avoids duplicate identities

  • Large companies might have same name - use unique keys like email to map identities

53
New cards

Provisioning

process of granting access

54
New cards

Birthright Access

default access automatically given to user based on rules/identity attributes

55
New cards

Connectors

integrations used by Sailpoint to connect with external systems

56
New cards

Workday

out of the box connector: import info then sailpoint connects to app

57
New cards

Custom connector

 new app that might not be out of the box, developer creates custom connector to tell sailpoint how to communicate with the app

58
New cards

HTTP Status code: (100-199)

Informational response

59
New cards

HTTP Satus code: (200-299)

Successful response

60
New cards

HTTP Status code: (300-399)

Redirection messages

61
New cards

HTTP Satus code: (400-499)

Client error response

62
New cards

HTTP Satus code: (500-599)

Server error response

63
New cards

BAU

Business as Usual

64
New cards

Identity Risk model 

Helps identify risk assessments to see which identity has the highest chance, or “loophole” where  cyber attack can happen

65
New cards

Service Account

Non-human account used to connect with other applications or to perform application-level access 

66
New cards

Privileged account

An account with more access

We have these to easily monitor access and keep accounts secure. These accounts are used less often, therefore they are less at risk for an attack

67
New cards

Dormant Account

Neglected accounts that are not used when original accounts gain problems and users get a new account

68
New cards

Syslog (System Logger)

Any errors that happens in the system, everything is recorded in this log

69
New cards

Organizational Role

Subordinants within a parent company

70
New cards

Business Role

Attach combination of IT roles and Entitlement roles

Assignment Criteria to both existing and new employees

71
New cards

IT Role

Combination of entitlements

72
New cards

Entitlement Role

This allows access to applications and can be assigned to roles

73
New cards

RapidSetup Birthright Role

Assigned to new employees when they begin

  • You can define assignment criteria and only add entitlements

74
New cards

Alert SOD

An email gets sent out when a policy is violated (post policy violation action item)

  • Revert changes, gets defined in the business process

75
New cards

Preventive SOD

An error occurs when someone tries to violate a policy