Desperate Hacker

Chapter 374 Stress Test

Chapter 374 Stress Test
  NASA!

Due to cost-cutting reasons, even space agencies now have many tasks outsourced.

In fact, the situation at home and abroad is similar on this point.

In general, the budget is only so much. After getting the budget, if you hire a large number of people!

It will definitely not be cost-effective in terms of capitation fee at that time.

Because once the project ends, many people will be idle.

So it is better to set up another company, hire these people in the form of a company, and when there is a project, recruit them into the project and do the hard work.

If not, you can also switch to serving other companies. Of course, a confidentiality agreement is required.

In fact, most of NASA's business is now done this way.

Even the tasks of launching rockets and carrying astronauts have been handed over to spaceX.

Prior to this, NASA had been leasing Russian rockets to transport astronauts to the space station.

In fact, not only NASA, but also Snowden, who caused a lot of trouble before, is not an employee of the CIA, but a senior technician of an outsourcing company.

……

A few months ago, NASA suffered a hacker attack.

Hackers stole approximately 240g of data.

Many of them involve sensitive information.

However, officials have denied the attack claimed by the hackers.

But the names and email addresses of those employees posted on the Internet are undeniable.

Therefore, this is the reasonable explanation given by NASA officials. Due to technical reasons, information on some less important positions and personnel has been made public.

But after the incident happened, the company responsible for security immediately took on the pressure of system security upgrades.

"These damn hackers!"

The engineer who had been working overtime for several weeks was sitting in front of the computer with dark circles under his eyes, angrily cursing at the hacker group who was looking for trouble.

Speaking of which, the overtime culture is not highly praised here.

But that's talking about employees who are largely unionized.

For some high-income people, such as the financial elites on Wall Street and some Silicon Valley technology companies with generous salaries, working overtime is actually an inescapable life.

Think about it, those Wall Street newcomers with annual salaries of hundreds of thousands of dollars are busy talking business with clients even when they are working out.

It’s not surprising that these highly paid engineers have spent several months here maintaining the contract with NASA!

The problem now is that although the system has found some problems, they are not easy to make up for.

The entire NASA system is subcontracted to multiple vendors.

For example, the operating system may come from Microsoft, or it may come from some other system companies.

Servers and data centers may use open source technology, or they may purchase services from some technical service companies!

Therefore, if we want to completely solve these troubles, we need the cooperation of all participating companies.

However, now NASA has pushed all problems to the security company!

There are some things that security companies can be responsible for, such as finding viruses, tracking hackers, recording traces, etc.!

But there are some things that even they can't do, such as how to fix it. It's not an internal error in the operating system written by their company!

……

Since there is no way to ask other companies to cooperate with their work, these engineers can only bite the bullet themselves and try to solve the problem with a method that treats the symptoms rather than the root cause!
  "Hey, Jack! Try it now. Try logging into the server the same way you just did?"

"OK!"

There are just a few ways hackers can invade!
  The first is to use your own script tool to scan!

See what loopholes exist in the system!
  The last time I attacked the opponent, I used a special scanning tool!    Apparently, engineers have now discovered the crux!
  At this time, the new version being tested has been officially deployed on the program and is undergoing the ultimate test of the test engineers!

The script ran very smoothly, and judging from the background server, the program they wrote completely withstood the test this time.

However, just when these people were about to be happy, suddenly!

"Wait a moment!"

"What's wrong? Everything goes well here?"

"It's a bit strange! Why is the resource usage so high?"

"Are you kidding? Did you forget another bug? It shouldn't be like this!"

Suddenly there was a loud buzzing sound from the office phone.

Jack, who was in charge of the test, picked up the phone and put it to his ear.

"What are you doing? Why can't I log in to the server now?"

"what are you saying!"

"What on earth are you doing with your test? Why can't I log in to the server?"

"This is impossible! Did you forget your password?"

"Are you kidding me? I have to log in to the server every day. I can't forget!"

Just when the phone call hadn't solved the problem, the phones in the office started ringing one after another.

Jack hurriedly picked up another phone and put it to his ear, but the other end of the phone cursed.

"Are you able to fix this vulnerability after working on it for several months? Why can't we access any data now?"

"I'm sorry, are we looking for a reason?"

"You better hurry up! Otherwise I will have to call the CEO of your company!"

"I'm sorry, sir!"

One call after another made the engineers who were busy testing at the site very anxious.

However, taking over a NASA project is like this. The rewards are huge, but there is also a lot of pressure.

But while Jack was busy answering the phone, his assistant was also verifying the problems one by one.

"Jack!"

"what?"

"What they said is true. I have also been kicked out of the server. Besides, it seems that I really can't get any resources now!"

"Hey! What are you doing?"

Test engineer Jack knocked on the glass partition window to ask what the man inside was doing.

As a result, I don’t know if it was because the sound insulation was too good, but the people inside just shrugged.

However, at this moment, suddenly the firewall alert popped up, and their system also flashed an intrusion prompt box!

Everyone was in a panic for a while.

"These damn hackers! They took over the system by force!"

"Find the problem quickly!"

……

Little did these engineers know that someone was using their system to do something big!
  And it was only for a few minutes that they lost control of the system!

Chen Qingfeng has got some things he wants.

Voyage records of aircraft and ships!
  And their communication keys! At this time, a submarine sailing near the Miyako Strait has completely exposed its own information!

(End of this chapter)

Tap the screen to use advanced tools Tip: You can use left and right keyboard keys to browse between chapters.

You'll Also Like