You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-user@db.apache.org by Steve Nobles <St...@smatrix.com> on 2012/12/04 02:08:25 UTC

Vetting Derby. Technical documents?

My company is evaluating whether to use Derby for a desktop/client-server application where security and 21-CFR 11 compliance is important. I'm looking for technical documents attesting to the robustness of Derby's security features. Something like unit test coverage/logs or the results of penetration testing. Third-party reports?

Thanks in advance!

Steve


Re: Vetting Derby. Technical documents?

Posted by Bryan Pendleton <bp...@gmail.com>.
> My company is evaluating whether to use Derby for a desktop/client-server
> application where security and 21-CFR 11 compliance is important.

Although Derby can be used perfectly well as a standalone database, it
is also designed to be embedded into a containing application.

The Derby libraries are small and stable, the memory footprint is
predictable, and many other aspects of Derby favor this embedded usage.

If you thus embed Derby into your application, you can arrange for little
or none of the Derby APIs to be part of the exposed "surface" of your
application, and therefore you can minimize your security exposure.

For example, you say you are designing a client-server application; presumably
Derby is to be part of the server component. But you do NOT need to make
Derby be the *entire* server component. As an alternative design, you could
implement your own completely locked-down web service, which provides
just the APIs that your application client requires, in a highly-secure fashion,
and embed Derby inside your secure web service.

Hope these ideas give you some new perspectives to consider.

thanks,

bryan

Re: Vetting Derby. Technical documents?

Posted by Steve Nobles <St...@smatrix.com>.
Knut Anders Hatlen <kn...@...> writes:

snip

> Hi Steve,
> 
> I'm not sure about all of the above, but at least there are unit test
> coverage reports here: http://dbtg.foundry.sun.com/derby/test/coverage/
> 


Thanks, Knut! Yes, that's useful.

I see 157K lines of code, covered 77% by 14K tests, with a single failure in 
the 10.8.2.2_RC version. In my experience that's a pretty darn good "batting
average."

I need something to compare it to.  (Hey, Google... )


Re: Vetting Derby. Technical documents?

Posted by Knut Anders Hatlen <kn...@oracle.com>.
Steve Nobles <St...@smatrix.com> writes:

> My company is evaluating whether to use Derby for a
> desktop/client-server application where security and 21-CFR 11
> compliance is important. I’m looking for technical documents attesting
> to the robustness of Derby’s security features. Something like unit
> test coverage/logs or the results of penetration testing. Third-party
> reports?

Hi Steve,

I'm not sure about all of the above, but at least there are unit test
coverage reports here: http://dbtg.foundry.sun.com/derby/test/coverage/

-- 
Knut Anders