Privileged Account Management- Types of Privileged Account

Types of Privileged Account

1. Elevated personal user account: Used by an end user with elevated/unrestricted  access, like IT admin or executives.
2. Shared privileged account: Unrestricted access to system to house sensitive data. Unix root account or windows admin, social media account.
3. Application Account:  Service accounts, This is used by applications to interact with each other.

Privileged Account Management- Types of User Account

Types of User Account

1. Regular user account: Identified by username, password and privilege, used by regular end user
2. Super User account: A special user account that can make system wide changes for all users.
3. Application account: This is used by applications to interact with each other without user interactive login procedure, typically stored in applications or data files.
4. Service Accounts: A service account is a special user account that an application or service uses to interact with the operating system

What is Privileged Access Management?

A privileged user/account is a user/account who holds the "key to the kingdom" i.e. the user/account has administrative access to the systems. They can carry out system wide configuration changes, lock/unlock other users, define and enforce system policies, install software, apply patches, access sensitive information etc. For instance, the individual who can set up and delete email accounts on a Microsoft Exchange Server is a privileged user.

“Privileged Account Management(PAM)” or “Privileged Session Management(PSM)” are generally interchangeable.

As is clear from the description of a privileged account, this access needs to be controlled, monitored and audited. Most cyber attacks target these privilege accounts to gain access to resources in any organization. PAM keeps your organization safe from accidental or deliberate misuse of privileged access. Most organizations have 3 times as many privileged users as employees.

PAM allows you the following high level capabilities:

• Grant privileges to users only for systems on which they are authorized.
• Grant access only when it’s needed and revoke access when the need expires.
• Avoid the need for privileged users to have or need local/direct system passwords.
• Centrally and quickly manage access over a disparate set of heterogeneous systems.
• Create an unalterable audit trail for any privileged operation.

What is Access control

Access control is the selective restriction of access to a place or other resource. The act of accessing may mean consuming, entering, or using. Permission to access a resource is called authorization.

Deploy Single HTML in Apache tomcat server

1. Create a folder in webapps folder e.g. 'CustomApp'
2. Put your html in this folder e.g. first.html
3. Start tomcat and point your browser to url "http://localhost:8080/CustomApp/first.html"

Note:

1. If the name of your html file is 'index.html', it can be simply opened by the url:http://localhost:8080/CustomApp

Installing and Running Apache Tomcat Server

1. Download apache server from https://tomcat.apache.org/
2. If the you have downloaded the zip, unzip at the location of your choice.
3. Create the following three environment variables
• CATALINA_HOME point to the unzipped apache tomcat location where the bin and conf folders are located.
• JAVA_HOME
• JRE_HOME
4. Execute 'startup.bat' from CATALINA_HOME/bin.
5. Open the link http://localhost:8080 to check if server is running

Eclipse: JAR v/s Runnable JAR

Both the types standard and runnable contains the Manifest file and java class files. The difference is in the content of Manifest file.

The Manifest file for runnable jar has an entry for main class:

Main-Class: com.kpmg.rohit.appraisalStrory.StoryTeller

That means runnable jar specifically specifies the entry point of jar. 

So if you just want to bundle your project in a library to be used by any application, any type of jar will suffice. But, say, you want to execute by command line, the difference will be clear

So, I have two jars for same project, one exported as runnable and other as standard jar

Let me try to run both of them via command prompt:

The runnable jar is executed but standard jar throws an error, because java does not the entry point to this jar.

We can explicitly specify the class with main method to execute the standard jar as well

That is it, hope you get it.