President Xi's and President Obama's agreement to curb economic cyberspying.

Question

Post reply

President Xi's and President Obama's agreement to curb economic cyberspying.

andrewbb

Old Hand

Points: 368
More actions
September 26, 2015 at 2:05 pm

#399098

I have the solution for President Xi's and President Obama's "economic cybersecurity". It solves application access. It works for law enforcement. There is no better or more powerful or simpler or more secure solution on planet earth.
How can I get it in front of decision-makers?
Sincerely,
Andrew B. Brown
PS. It is an emergency.
PS 2. It consists of 3 pipelines to the database:
Database.Store
Database.Delete
Database.Load
It is as simple as that.
PS. 3. Please hold off all discussions on "cryptoblah" until this solution is reviewed.

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply

Jeff Moden SSC Guru Points: 1004362 More actions · Answer 1

There are two problems with you're good solutions, IMHO...

1. They're usage is not enforceable.

2. They only address a small part of the problem.

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

andrewbb Old Hand Points: 368 More actions · Answer 2

Jeff Moden (9/27/2015)
There are two problems with you're good solutions, IMHO...
1. They're usage is not enforceable.
2. They only address a small part of the problem.

It is a significant part because it funnels all access through a single interface. Easy to use and impossible to screw up. Prevents SQL injection and hides the data table structure. It allows centralized logging and supports any granularity in securing objects.

I am trying to get it communicated to various governmental entities in Texas with the goal of having it as a standard interface to all RDBMS's.

It is powerful as can be and trivial to get it working.

Jeff Moden SSC Guru Points: 1004362 More actions · Answer 3

andrewbb (9/27/2015)
Jeff Moden (9/27/2015)
There are two problems with you're good solutions, IMHO...
1. They're usage is not enforceable.
2. They only address a small part of the problem.
It is a significant part because it funnels all access through a single interface. Easy to use and impossible to screw up. Prevents SQL injection and hides the data table structure. It allows centralized logging and supports any granularity in securing objects.

No doubt you could make it more difficult to "get hacked" but your good method is not able to stop the human trait of making mistakes and poor decisions. Just because there is an interface doesn't stop people from bypassing the interface or even using the interface to get what they want. For example, many of the break-ins that have made the headlines have had nothing to do with an interface. Rather they've been logins that are allowed... by the wrong people because some idiot gave up his login and password. Even habits of people can be exploited to allow a super secure "interface" to be penetrated. Turing proved that in WWII.

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

andrewbb Old Hand Points: 368 More actions · Answer 4

Jeff Moden (9/27/2015)
andrewbb (9/27/2015)
Jeff Moden (9/27/2015)
There are two problems with you're good solutions, IMHO...
1. They're usage is not enforceable.
2. They only address a small part of the problem.
It is a significant part because it funnels all access through a single interface. Easy to use and impossible to screw up. Prevents SQL injection and hides the data table structure. It allows centralized logging and supports any granularity in securing objects.
No doubt you could make it more difficult to "get hacked" but your good method is not able to stop the human trait of making mistakes and poor decisions. Just because there is an interface doesn't stop people from bypassing the interface or even using the interface to get what they want. For example, many of the break-ins that have made the headlines have had nothing to do with an interface. Rather they've been logins that are allowed... by the wrong people because some idiot gave up his login and password. Even habits of people can be exploited to allow a super secure "interface" to be penetrated. Turing proved that in WWII.

I agree. However, it eliminated one source of ambiguity. Then, the more esoteric back doors can be identified and closed.