# Elevated Persistence

These methods are achieved once the operator has elevated its persistence on the workstation, this is helpful to avoid the privilege escalation situation and just come back to a higher permissions shell.

Note: These will require Privilege Escalation beforehand to achieve this level of persistence

Services

Services may be created with Administrator privileges, but they are executed under the SYSTEM level privileges, services can also be started through Service Execution.

A demonstration of the level required to create a Service can be shown below

![](https://315180959-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MRh03Vwd4nuiUi3Oje7%2Fuploads%2FF7B2fXkArjK8YLumko8o%2Fimage.png?alt=media\&token=a5f34a71-fc5f-43e1-9c9f-60fcce4bbcf8)

But once elevated  to the Administrator level

![](https://315180959-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MRh03Vwd4nuiUi3Oje7%2Fuploads%2FCU0OMqXuulPOaajQdhYH%2Fimage.png?alt=media\&token=5cf4281b-a9cf-49f0-849f-8e9bef98775f)

Our service has been successfully created and it's currently stopped will proceed to start the service

![](https://315180959-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MRh03Vwd4nuiUi3Oje7%2Fuploads%2FtEzSo5U7zoN73d8U3A43%2Fimage.png?alt=media\&token=4bb48d0a-7d7f-49ff-98c0-2a90112f652d)

Even when the service lags or executes with an error it is still run successfully this usually happens when you replace the beneath with a command instead of a binary

![](https://315180959-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MRh03Vwd4nuiUi3Oje7%2Fuploads%2FGmUlZh02zS9wJEdPoAxn%2Fimage.png?alt=media\&token=229da1b2-ba08-48c8-8745-c89695fc70a7)

All methods of persistence are available at this level of access on the workstation, I just wanted to demonstrate a specific one that can be demonstrated easily when Administrator access is needed.