Blockchain Based IT Database

I am here to present the next level for databases in IT. By implementing a base

themed after current Blockchain coding, a new way to secure peer information could arise.

This would be a result of how these databases trap information and lock it as it is being

input. While it may seem that this could have its drawbacks, this type of system would

encourage secure data management, create less instances of forgetfulness, and result in

less data breaches due to its centralized nature. With an accommodable UI that promotes

user leisure, employees in IT will have a greater incentive to be detailed in their notes as

well as in keeping track of tickets and orders of equipment, for example. This idea came

following the current trends of multimillion dollar companies being hacked into by regular
people like us. Companies with this much of a social stance should not be brought into a

bad light like this and neither should their hardworking employees be in fear of losing their

Personal Information at any given moment. Unfortunately it has happened far too many

times in acts of data breach to the point where it almost feels hopeless to fight against it. In

a way, this idea is made to be an unlikely combination with full intent because that can give

a further advantage into protection against malware. Both human and technology evolve

around the many patterns that we unknowingly take, and because of that fear of change is

why some entities become more vulnerable to attacks as the days go by. With this slight

switch up, it could hopefully be the start of a new and more secure way to store and

receive information.

In the setting of IT, keeping track of past data is crucial due to a multitude of

reasons. Receiving and removing a ticket from its different statuses is one of many

examples of how data travels all around an IT department. Any time where data is exposed

in travel like this is still a vulnerability even when it is not exposed outside the company. In

a Blockchain by providing signatures to the code after inserting data is used to keep it
secure and interoperable. In this innovation it is crucial to stay by its roots while also

making something that is beyond just Cryptocurrency.

Timeline in mind it looks to be that this implementation would take months to even

close to a year if all things are considered. That is why I have scoped out the scale of this

including major tasks such as the networks configuration, design, development, and

deployment. This timeframe would involve the proper training for the IT department to

adapt to the new and more strict procedure of data collection/record keeping. Topics such

as the type of code used to develop will be determined through this testing process while

every other preparation proceeds to culminate.

 Since this is an innovation rather than a copy/paste of a Blockchain, we are hoping

to strike a balance in regard to data editing and errors in it. In a standard Blockchain

removal of data is incredibly difficult due to its uses of Cryptographic hashing, its state of

immutability, consensus mechanisms, and its decentralized nature. I see how if this was a

straight Blockchain to IT transfer that it would cause problems when it comes to record

keeping and ticket follow ups due to hashing, however if we take parts of this and

implement it to a more lenient atmosphere it could greatly increase the security in the IT

department. It is a goal to move from the strict hashing of the data input but we would have

a limit on number of accesses in a certain amount of time to prevent outside sources from

seeing that information. Having this limit while also keeping a trait of the hashing

implemented so that the database can still be highly immutable while also not serving as a

nuisance to the IT workers.

With all those secure traits, this type of database can also bring a new sense of

transparency, efficiency, and cost-saving because of proper implementation. This type of

database will provide an easier method of data tracing by its use of a shared/transparent

ledger that will be accessible to all network workers. This advantage will bleed into other

growth topics such as performance feedback, communication skills, and an emphasis on

teamwork. Ultimately the innovation of a Blockchain based IT Database is mainly brought

up to improve the security of these departments. We are currently in an era where even big

companies can be just as vulnerable to data breaches as the average person is. With IT

departments constantly relaying information including those that involve companywide

issues, if any outside source got hold of that information it could lead into an easy pathway

in to attack those systems as IT departments hold on to notes on what is currently

vulnerable while they try to fix it. And as mentioned before, Blockchains have had a

different representation rather than to IT like this. However, that shift in tactics could end

up saving a whole lot of trouble from occurring,