Preferences

Airbus is putting all its design on internet? wow...

You can have the data safely on-prem, connected to computers that are connected to the internet, or safely in the cloud, connected to computers that are connected to the internet. The threats are not that different.
Managing product data on the cloud does not mean public internet access, unless someone messes something up big time.
You'd be fooling yourself if you think any moderately complex company still hasn't moved to the cloud or isn't thinking about it (with rare exceptions)
Yeah, not really sure how a globally distributed manufacturing operation with a complex supply chain and customers all over the world that need access to data for their operations is supposed to function effectively without it.

(and I say that as someone that used to sell commercial aviation data that came on CDs...)

I don't think this is related to that "critical" stuff.

It seems there is a misunderstanding over the classification of 'critical' stuff.

We may all have a very different definition.

All I know: the second your are connected to internet, you are cooked.

I'm not sure what the 'critical' stuff is either or what the details of Airbus' network hosting and knowledge compartmentalization strategy is, but you're not going to run a globally distributed manufacturing business with complex supply and maintenance requirements without having technical specs, CAD files, diagnostic criteria customer records etc sitting on computers connected to the internet.
You do know that the Internet and "the cloud" are not the same thing, right?
> Airbus is putting all its design on internet? wow...

Not only Airbus. You see, cloud is secure, information is encrypted and only you have access to your data.

It would be reasonably "secure" if it is encrypted on a physically private network using in-house _modified_ _mainstream_ encryption algorithm, then after an over-the-air transfer then you can store it on a third party could under the control of foreign interests. Oh, don't forget the file names have to be encrypted too.

Everything else is, I am sorry to say, BS.

> in-house _modified_ _mainstream_ encryption algorithm

Why would a company without cryptographic expertise modifying an existing algorithm without any particular goal in mind just to be different, produce something more secure than the winning solution in an open cryptographic competition?

> directory names

And file structure too, preferably. Incremental sync could be done with XTS mode.

You need only cryptographic common sense: it seems you have no idea how much it is easy to modify a mainstream cryptographic software to add basic and robust cryptographic modifications...

Are you an AI?

I've been assessing systems that use cryptography for about 20 years as part of my work in information security, and I've never seen a customization that increased the security of a cryptographic algorithm over following the best practices.

Usually, non-specialists fiddling with cryptographic algorithms makes them much less secure. Developers who aren't cryptographic mathematicians should generally use a well-respected algorithm, follow current best practices, and treat that component as a magic box that's not to be tampered with.

>You need only cryptographic common sense

Sounds like the "I know a guy" kind of thing that shouldn't be done if you really care about security.

>Are you an AI?

Non-sequitur.

This item has no comments currently.

Keyboard Shortcuts

Story Lists

j
Next story
k
Previous story
Shift+j
Last story
Shift+k
First story
o Enter
Go to story URL
c
Go to comments
u
Go to author

Navigation

Shift+t
Go to top stories
Shift+n
Go to new stories
Shift+b
Go to best stories
Shift+a
Go to Ask HN
Shift+s
Go to Show HN

Miscellaneous

?
Show this modal