Skip site navigation (1) Skip section navigation (2)

Re: [PATCH] SE-PgSQL/tiny rev.2193

From: KaiGai Kohei <kaigai(at)ak(dot)jp(dot)nec(dot)com>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org, Joshua Brindle <method(at)manicmethod(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Martijn van Oosterhout <kleptog(at)svana(dot)org>, KaiGai Kohei <kaigai(at)kaigai(dot)gr(dot)jp>
Subject: Re: [PATCH] SE-PgSQL/tiny rev.2193
Date: 2009-07-22 08:30:55
Message-ID: 4A66CE3F.8090805@ak.jp.nec.com (view raw or flat)
Thread:
Lists: pgsql-hackers
Peter Eisentraut wrote:
> On Monday 20 July 2009 17:52:44 Joshua Brindle wrote:
>> That is your (and the communities) prerogative. Linus wasn't very
>> supportive of SELinux in the kernel either but it is the only way Linux got
>> an EAL4+ LSPP evaluation for use in certain government systems. I
>> personally would love to see an open source DBMS evaluated for systems like
>> this because the current state of the art is fairly sad.
> 
> This would actually be a reasonable baseline to work against, if we define a 
> project goal to be satisfying this standard.
> 
> This is presumably the web site that describes this standard: http://www.niap-
> ccevs.org/cc-scheme/pp/pp_os_ls_v1.b/  There I see
> 
> Succeeded By:  pp_os_ml_mr2.0_v1.91  
> Sunset Date: 16 September 2007
> 
> And the successor document is vastly more comprehensive than implementing a 
> MAC scheme.

The target of this protection profile is operating system,
so it is a bit mismatch.

Referring to the prior case, Oracle Label Security (it also provides
label based access controls, but no collaboration with OS) is cerfified
with the BR-DBMSPP (U.S.Government Protection Profile Database Management
Systems For Basic Robustness Environments) and additional functional
components (such as FDP_IFC.1: Subset Information Flow Control,
FDP_IFF.2: Hierarchical Security Attributes, and so on).

http://www.commoncriteriaportal.org/products_DB.html#DB

* ST for Oracle Label Security for Oracle Database 10g Release 2
http://www.commoncriteriaportal.org/files/epfiles/20080306_0402b.pdf

> So how do we realistically get from here to there (and where is "there")?

Security functionality is a factor to get ISO/IEC15408 certification,
but not all. (For example, who can defray the cost for evaluation?)
However, it is important to pull up the baseline functionality to
satisfy these security functional components.

If certification is only valid on the "patched" version, rest of people
will not be happy.

-- 
OSS Platform Development Division, NEC
KaiGai Kohei <kaigai(at)ak(dot)jp(dot)nec(dot)com>

In response to

pgsql-hackers by date

Next:From: Laurent LabordeDate: 2009-07-22 08:54:02
Subject: Re: Higher TOAST compression.
Previous:From: Fujii MasaoDate: 2009-07-22 07:56:47
Subject: Re: Non-blocking communication between a frontend and a backend (pqcomm)

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group