Information Security: Difference between revisions

From Secure Group Wiki
Jump to navigation Jump to search
mNo edit summary
m (Sgadmin moved page System Administration to Information Security without leaving a redirect: changing the name of the framework)
(No difference)

Revision as of 15:46, 27 October 2020

Our Systems Administrators are responsible for coordinating computing environments, deploying and documenting routines and projects controlling the service levels of operating systems, databases and networks.

They provide technical support in the use of computer hardware and software and in supporting users by configuring and installing computing resources and systems controlling the security of the computing environment, which is our number one driver.

It is under the responsibility of the Systems Administrators to work with the configuration and maintenance of the systems' environment, from performance monitoring and availability of the systems, to the definition and monitoring of system infrastructure's suppliers and to make the configuration and maintenance of backups, performing the installations and configurations of the operating systems.

In order to progress in our development path and Level Up or Step Up, our System Administrators must:


Salary Grid

All mentioned salary ranges represent the monthly income in Bulgarian Lev after taxes and deductions.

System Administration Step
Level
Individual Contributor Path 1 2 3 4
System Administrator 1.800 1.950 2.100 2.250
Sr. System Administrator Level 2 2.800 2.950 3.100 3.250
Network Engineer Level 3 3.800 3.950 4.100 4.250
Sr. Network Engineer Level 4 4.800 4.950 5.100 5.250
Network Architect Level 5 5.800 5.950 6.100 6.250
Sr. Network Architect Level 6 6.800 6.950 7.100 7.250

KAI of the position

General Knowledge

Concepts Balanced Scorecard
Scrum
Frameworks Scrum
Softwares/Tools/Platforms - Usage Atlassian Bamboo
Atlassian Confluence
Atlassian Jira
BambooHR
Countly
Docker Harbor
Gerrit
Lansweeper
Libib
OpenSTF
Paessler PRTG
Small Improvements
Tableau
Thycotic Passwordbox
Softwares/Tools/Platforms - Configuration Atlassian Bamboo
Atlassian Confluence
Atlassian Jira
Countly
Docker Engine/Container
Docker Harbor
Gerrit
Lansweeper
Microsoft Dynamics Navision
OpenSTF
Paessler PRTG
Samsung Knox
Tableau
Softwares/Tools/Platforms - Server Administration Atlassian Bamboo
Atlassian Bitbucket
Atlassian Confluence
Atlassian Jira
Countly
Docker Engine/Container
Docker Harbor
Gerrit
Lansweeper
Microsoft Dynamics Navision
OpenSTF
Paessler PRTG
Samsung Knox
XiboTV
Protocols NFS
Languages (Idioms) Advanced English

IT Knowledge

Android Development
Programming

Secure Group Knowledge

The first item we require proficiency regarding our company is the Secure Group Management Model (yes, the content in this wiki!). Besides that, we also need our employees to understand our products in all aspects as described in the following table:

Secure Group Knowledge What's Expected Impact Product Minimum Grade
User Documentation Good, user-level knowledge regarding the product and its functionalities. From the user documentation, all employees across the company are required to be well aware of our solutions’ core features and functions such as the Password Advisor or how to send an automatic crash report. This knowledge helps us facilitate a user-centric approach internally, which we believe is essential to develop our business and solutions. The user documentation helps team members understand user behavior and needs more thoroughly and feel the impact of their everyday efforts. Secure OS 4
SAS 4
Secure Chat 4
Secure Email 4
Secure Vault 4
Secure Manager 4
Sales Documentation Employees should gain significant knowledge regarding the business side of Secure Group. They need to be aware of commonly used concepts in our day-to-day activities such as our business and distribution model, value proposition, selling prices, key selling points, and target audience. The information in the Sales Documentation supports employees in their daily routine. It conveys the overall business vision within the company. This documentation contributes to making employees aware of how our solutions are distributed, who are our key partners and target market to know exactly the people towards whom team members’ efforts should be aimed. Alignment on company-wide priorities is also achieved through clear communication of our value proposition and key selling points, helping everyone understand the things that matter most. Secure OS 3
SAS 3
Secure Chat 3
Secure Email 3
Secure Vault 3
Secure Manager 3
Support Documentation People within the company need to be aware of commonly occurring problems with our solutions. From the Support Documentation, employees should also extract general level knowledge regarding support processes, the issues that we’re currently having product-wise, and the approach to troubleshooting them. o The Support Documentation helps employees understand short-term priorities more clearly and communicate more openly why they’re needed. It also gives them general knowledge of how to spot and report a problem, which helps us facilitate a company-wide contribution to product development. Last but by no means least, it helps team members understand customers pains and behavioral patterns to strengthen our user-centric approach. Secure OS 3
SAS 3
Secure Chat 3
Secure Email 3
Secure Vault 3
Secure Manager 3
Functional Documentation Through the Functional Documentation, employees should get a thorough understanding of the solutions and their multiple features. People that work closely with the products must understand exactly how they function, how users interact with them, how to configure different settings, and what’s the expected behavior of different software solutions. o The information in the Functional Documentation helps employees whose work is closely connected with our solutions, to gain significant in-depth knowledge into their functionalities that far exceeds users‘ understanding. Such thorough product expertise helps us remain objective, evaluate market data more adequately, and constantly increase our internal expertise. Secure OS 4
SAS 4
Secure Chat 4
Secure Email 4
Secure Vault 4
Secure Manager 4
Technical Documentation Employees concerned with the Technical Documentation and more concretely - software development, must gain complete mastery over all solutions. Such people are regarded as technical experts and need to be well aware of data structures, relational databases, algorithms, programming languages, models, etc. The Technical Documentation is used to make sure people that are technically involved in product development have the required knowledge to perform their day-to-day tasks, optimize our solutions more easily, and support other teams with their in-depth expertise. Secure OS 4
SAS 4
Secure Chat 4
Secure Email 4
Secure Vault 4
Secure Manager 4
Retrieved from "https://managementmodel.info/index.php?title=Information_Security&oldid=1346"