Re: I need a system the U.S. government cannot 'hack'

From: karl levinson, mvp (levinson_k_at_despammed.com)
Date: 11/27/05 

Date: Sun, 27 Nov 2005 07:31:04 -0500

"Proprietor_PER_Ltd" <ProprietorPERLtd@discussions.microsoft.com> wrote in
message news:BFE867EF-94F7-42A7-8B26-C7984B111D40@microsoft.com...
> Sir:
>
> To begin with, I am not working on a 'hypothesis'. I have in fact spent
> 23
> years learning my craft -->

Dictionary.com defines hypothesis as something that "can be tested by
further investigation." Unless you're running your system of government on
an island somewhere with actual people, I would describe it as untested.

> Second, I have in fact already designed a machine which I believe will
> meet
> the security requirements of this application, however, moving forward
> requires two things: proper vetting of that design by 'the public' (that
> segment of it interested in, and/or with a professional interest in,
> security) and due consideration of competing alternatives.
> The purpose of my post is to find alternatives -->

I must say it seems unlikely that you have designed a database that cannot
be hacked... even if you were a database expert who is already intimately
familiar with alternative secure database designs out there. Everything can
be hacked, if not now, then in the future.

Relevant Pages

  • Re: doctors office database
    ... keep in mind the HIPAA privacy and security requirements, ... > a database program that keeps track of patients, ... > This post is a suggestion for Microsoft, ...
    (microsoft.public.access.tablesdbdesign)
  • Re: Row level security in n-tier applications
    ... to create a framework where new security requirements do not require tinkering with the database, ... The idea should be to create a framework where a change in the security ...
    (borland.public.delphi.non-technical)