
|
Contact
Us with questions, comments, or praise | ©2008 BMC Engineering
To provide system access to physicians, physician staff,
and clinicians To protect the confidentiality of patient and administrative
information To maintain system integrity and security as defined by the
organization To comply with HIPAA regulations as set forth by the Federal
Government Any clinician requesting access to the Hospital Information
System (HIS) system will notify the Information Services (I.S.) Department.
An information packet will be sent to the requesting clinician. This
packet will include Request forms, profile questionnaire, security policy,
and hardware/system requirements Once the request form and questionnaire
have been returned to I.S., user codes and passwords will be defined.
A signed confidentiality statement will be obtained and kept on file
in the I.S. department. Under no circumstances should this code be shared
with anyone else. All computer transactions are traced through this code
and is audited daily by the Information Services Department. You will
be responsible for all inquiries made under your security code. Patient
information in the organization’s computer system is to be kept
confidential and private as per HIPAA and Florida State regulations.
Health care organizations have toiled for years to implement policies
and procedures to comply with the HIPAA Privacy Regulations. April 14,
2003 has come and gone, and HIPAA Privacy is no longer a questionable
regulation, it is a reality. No matter how much you would like to take
a break from HIPAA, there is still work to be done. get really disheartened
when I heard most arguments urging attorneys to encrypt their e-mail.
For several years now, I've heard selected attorneys and consultants
say "e-mail can be intercepted," "people are interested in reading YOUR
e-mail," "e-mail is like a postcard," "there are malpractice concerns
associated with transmitting unencrypted e-mail," or "e-mail interception
happens all the time -- people are just to embarrassed to admit it." These
arguments typically attorney client security conclude that given one
or more of these risks (perhaps called "facts"), attorneys should encrypt
their e-mail communications. End of story. What standard of encryption
is good enough for HIPAA? Well, the new HIPAA Security Rule seems to
leave the choice up to you. Good enough encryption for HIPAA should mean
that the software employs time-tested encryption algorithms which can't
be penetrated by someone with dedicated tools or governmental deciphering
resources, if at all. Examples of these are DES, AES, RSA, Blowfish,
Twofish. No algorithm GUARANTEES total security against the various types
of security attacks that professional hackers can employ (see Adam Benrent's
paper But "good enough encryption" for your purposes is available in
a plethora of free or cheap products, including my personal favorites:
The problem with this story is that it is incomplete, thereby failing
to educate properly the audience it is intended to help. Attorneys are
told that encryption is the answer to deal with the real threat their
client confidences and secrets will be disclosed. Unfortunately, attorneys
are left to their own devices to plan and implement encryption (and hopefully
other measures) to address the overarching security issues associated
with protecting client confidences and secrets. What level of encryption
is appropriate? Will it work with the attorney's system (perhaps better
to say systems) and all clients' systems? Is it foolproof? How do I manage
the keys within my organization? How do I recover encrypted files after
someone leaves within the organization? How can encryption be implemented
in [fill in the blank (my organization -- governmental agency, pro bono
referral network, legal services agency, corporation, corporate law firm,
shared office space, …)]? Like most technical issues, the issue
of whether to adopt encryption is not so simple. There are a host of
issues associated with attorney client security integrating a technical
solution into an existing corporeal practice. Perhaps the most important
issue attorneys need to understand is that encryption products are simply
software. As such, they cannot possible be the only answer to real or
perceived threats to the security of client confidences and secrets.
To quote Bruce Schneier, author Secrets & Lies: Digital Security
in the Networked World, "If you think technology can solve your security
problems, then you don't understand the problems and you don't understand
the technology." Secrets & Lies (J. Wiley & Sons 8/2000) at xii.1
Encryption -- or any technology for that matter -- is only effective
only if it is treated as part of a much larger process. Here, I reflect
on some of the issues that attorneys should consider as they delve into
the encryption issue. Before I begin, three points to provide some context.
E-mail may be an efficient and cost effective way of transmitting data,
but how secure is this method of information distribution? Many e-mail
messages contain information that could be regarded as sensitive by either
the sender or the receiver. In the case of the health care industry,
messages may even include Electronic Protected Health Information (ePHI).
ePHI is defined as being individually identifiable information that is
maintained in any form by a health plan, clearinghouse, or provider and
related to health condition, treatment, or payment. The Health Insurance
Portability and Accountability Act (HIPAA) requires health care institutions
to comply with information privacy and security standards. Many of these
institutions have drafted policies that forbid the transmission of protected
health information via e-mail. Other institutions which have local area
networks have permitted the transmission of protected health information,
but only to other employees on the institution’s local computer
network. While neither the HIPAA privacy nor security rule expressly
requires it, most security professionals believe secure Internet e-mail
is a reasonable step for a health care institution to take in order to
abide by the HIPAA requirement to “ensure the integrity and confidentiality” of
ePHI. (i) I do not propose any easy solutions to the encryption issue.
I intentionally raise more questions than I answer. The reader should
come away asking questions instead of blindly following encryption advocates
and relying upon encryption products. (ii) I like encryption products.
They have appropriate -- and sometimes necessary -- uses. I believe that
encryption products can be powerful tools that go a long way to help
protect client confidences and secrets when (1) those products and associated
processes/procedures are thoughtfully integrated into an attorney's practice;
(2) those products and those processes/procedures are thoughtfully integrated
into a client's business or situation; and (3) both sets of products
and processes/procedures are thoughtfully implemented and maintained
by all parties. In short, when a security protocol partly based on encryption
products is integrated into one's practice after careful consultation
with one's clients, it can be a powerful solution. If encryption products
are integrated into an attorney's practice in the absence of any consideration
of larger security processes followed by the attorney or organization,
they can be dangerous tools. (iii) I take as a baseline assumption that
e-mail is not secure. The reader should as well. Snooping and interception
are realities, regardless of the amount of money involved. It is relatively
easy to gain access to computer systems. If you want a "parade of horribles" relating
to the lack of security on the Internet or relating to computers generally,
pick up Schneier's Secrets & Lies. It provides the necessary examples
and context. The analogy to a postcard does not. Get Some Ethical Perspective "Confidential
client information must be 'acquired, stored, retrieved, and transmitted
under systems and controls that are reasonably designed and managed to
maintain confidentiality.'" ABA 99-413 n.4, quoting Restatement (Third)
of the Law Governing Lawyers, §112, Cmt. d (proposed official draft 1998).
Some attorneys and reporters look to ABA 99-413 as "the answer" on encryption.
It is not. ABA 99-413 does not say that you do not need to encrypt your
e-mail. In ABA 99-413, the ABA Standing Committee on Ethics and Professional
Responsibility simply took a comparative look at the issue of how to
protect client confidences and secrets that are transmitted by e-mail.
The Committee found that transmission of unencrypted e-mail after consultation
with the client advising the client of the risks involved was a reasonable
way to exchange client information.2 Importantly, the Committee considered
the fact that there are risks associated with the way attorneys handle
other forms of client communications. The reader should too. The latest
ethics opinions issued to date in the jurisdictions that have addressed
the issue seem to agree with the overall reasoning of ABA 99-413. I do
too.3 As suggested below, an alternative approach would be, for most
attorneys and clients, undesirable and unreasonable given its logical
extension. best way to hide pictures Sort by Area Hide Photos files,
folders, and drives so you can encrypt, decrypt, wipe files and folders
with right-click ease able to encrypt photos or drawings contained in
a text file Encrypt, File Encryption, Encrypting, Encrypt files, Self
decrypt ... pictures,download picture, File Encryption, Data Encryption,
personal Encryption, Message Encryption, E-Mail Encryption, E mail Encryption,
email encryption, download photo, download photos, Picture Encryption.
search picture Encrypt photos so that unauthorized eyes cant see them
You can encrypt your photos to prevent viewing by unauthorized people
you can encrypt email you send to them by clicking on the encrypt button.
you are only able to encrypt this email if you have the public key of
the recipient. If you attempt to Encrypt secure and protect any email
message from any email program with Encrypt Pictures, Directories, Files,
Spread Sheets, Picture Encryption. Word Processor Documents,E-Mail! Extremely
Strong File Encryption, Data Encryption, personal Encryption, Message
Encryption, E-Mail Encryption, E mail Encryption, email encryption, Encryption
Software Encrypt Pictures and Multi-Media files Encrypt pictures and
media before burning on to CD. Hide your private files from other users
of your PC new encryption utility which is aimed at providing Hide photos
and posters Hide music and CDs Hide VHS and DVDs. hide pictures, Product
information Steganography Digital Watermarking -Information Hiding -.
... Steganography: Steganography paper This is where File Encryption,
Data Encryption, personal Encryption, Message Encryption, E-Mail Encryption,
E mail Encryption, email encryption, steganography can come into play.
Steganography simply takes steganography for Windows. Includes Sort by
Area Hide Picture Encryption. Photos files, folders, and drives so you
can encrypt, decrypt, wipe files and folders with right-click ease able
to encrypt photos or drawings contained in a text file Encrypt, File
Encryption, Encrypting, Encrypt files, Self decrypt ... pictures, download
cture, download photo, download photos, search picture Encrypt photos
so that unauthorized eyes cant see them You can encrypt your photos to
prevent viewing by unauthorized people you can encrypt File Encryption,
Data Encryption, personal Encryption, Message Encryption, E-Mail Encryption,
E mail Encryption, email encryption, email you send to them by clicking
on the encrypt button. you are only able to encrypt this email if you
have the public key of the Picture Encryption. recipient. If you attempt
to Encrypt secure and protect any email message from any email program
with Encrypt Pictures, Directories, Files, Spread Sheets, Word Processor
Documents, E-Mail! Extremely Strong Encryption Software Encrypt Pictures
and Multi-Media files Encrypt pictures and media before burning on to
CD. Hide your private Picture Encryption. files from other users of your
PC new encryption utility which is aimed at providing Hide photos and
posters File Encryption, Data Encryption, personal Encryption, Message
Encryption, E-Mail Encryption, E mail Encryption, email encryption, Hide
music and CDs Hide VHS and DVDs. hide pictures, Product information Steganography
Digital Watermarking - Information Hiding -. ... Steganography: Steganography
paper This is where steganography can come into play. best way to hide
pictures Steganography simply takes Steganography for Windows. Includes
Sort by Area Hide Photos files, folders, and drives so you can encrypt,
decrypt, wipe files and folders with right-click ease able to encrypt
photos or drawings contained in a text file Encrypt, File Encryption,
Picture Encryption. Encrypting, Encrypt files, Self decrypt ... pictures,
download picture, download photo, download photos, search picture Encrypt
photos so that unauthorized eyes cant see them You can encrypt your photos
to prevent viewing File Encryption, Data Encryption, personal Encryption,
Message Encryption, E-Mail Encryption, E mail Encryption, email encryption,
by unauthorized people you can encrypt email you send to them by clicking
on the encrypt button. you are only able to encrypt this email if you
have the public key of the recipient. If you attempt to Encrypt secure
and protect any email message from any email program with Encrypt Pictures,
Directories, Files, Spread Sheets, Word Processor Documents, E-Mail!
Extremely Strong Encryption Software Encrypt Pictures and Multi-Media
files Encrypt pictures and media before burning on to CD. Hide your private
files from other users of your PC new encryption utility which File Encryption,
Data Encryption, personal Encryption, Message Encryption, E-Mail Encryption,
E mail Encryption, email encryption, is aimed at providing Hide photos
and posters Hide music and CDs Hide VHS and DVDs. hide pictures, Product
information Steganography Digital Watermarking -Information Hiding The
block cipher Rijndael The Rijndael book is out We finally finished this
book. Besides a clear, flawless description of our algorithm, the book
also contains a description of all the implementation tricks we know
about, a thorough explanation of our design strategy and the Picture
Encryption. underlying motivations, an overview of the cryptanalytic
results on reduced versions of Rijndael, an overview of related ciphers,
and some more. The book also contains some previously unpublished results
on extending Matsui's linear cryptanalysis to ciphers defined in GF(256)
it's published by Springer-Verlag, ISBN 3-540-42580-2.Rijndael becomes
AES You probably know it already, maybe it's the reason File Encryption,
Data Encryption, personal Encryption, Message Encryption, E-Mail Encryption,
E mail Encryption, email encryption, why you're here at this page. We
happily refer you to the Rijndael fan page for more news. Flemish Personality
Award CaStaR - Personality of the year Because of Rijndael's selection
as AES, we have been selected as (Flemish) personalities of the year.
As a consequence, we were rewarded with the piece of art you see on the
right. The colored specks on the skull and the bones are in fact the
shields of a rare beetle. Some people say it symbolizes the DES (bird)
being replaced by the AES (skull). Others think that the Flemish watch
too much MTV. What is Rijndael Rijndael is a block cipher, designed by
Joan Daemen and Vincent Rijmen as a candidate algorithm for the AES The
cipher has a variable block length and key length. We currently specified
how to use keys with a length of 128, 192, or 256 bits to encrypt blocks
with al length of 128, 192 or 256 File Encryption, Data Encryption, personal
Encryption, Message Encryption, E-Mail Encryption, E mail Encryption,
email encryption, bits (all nine combinations of key length and block
length are possible). Both block length and key length can be extended
very easily to multiples of 32 bits. Rijndael can be implemented very
efficiently on a wide range of processors and in hardware. The design
of Rijndael was strongly influenced by the design of the block cipher
Square .Publications Besides the documents available from this web site,
a number of (technical) Rijndael-related papers have been published.
Picture Encryption. We give here an overview. J. Daemen, V. Rijmen, ``The
Block Cipher Rijndael,'' Smart Card Research and Applications, LNCS 1820,
J.-J. Quisquater and B. Schneier, Eds., Springer-Verlag, 2000, pp. 288-296.J.
Daemen and V. Rijmen, ``Rijndael, the advanced encryption standard,''
Dr. Dobb's Journal , Vol.~26, No.~3, March 2001, pp.~137--139. If you
are looking for a Rijndael reference, then please use one of these. Pictures
and animations Being not very at home in the graphical department, we
refer you happily to the pictures made by John Savard. Enrique Zabala
from Uruguay made a very nice Picture Encryption. animation showing the
operation of Rijndael. Download The following files File Encryption,
Data Encryption, personal Encryption, Message Encryption, E-Mail Encryption,
E mail Encryption, email encryption, are available for download: Answer
to the observations on the Rijndael diffusion layer, recently submitted
to the NIST AES forum. Updated documentation and complete specification
, as required by NIST (Adobe PDF format). This version Picture Encryption.
corrects the errors that were found in the original document. NOTE: after
Rijndael was selected to become AES, it was decided to change the names
of some subroutines. The new names have been used in all our subsequent
publications (including the book). The paper here is provided for reasons
of historical interest only. Please use the description available from
NIST's website. A more theoretic paper , detailing the design principles
behind Rijndael (Adobe PDF format). A document on efficient implementation
of the S-box in hardware. Java code , for use with the Cryptix toolkit
.Reference code in ANSI C v2.2. Optimized C code v3.0 (code provided
by Paulo S.L.M. Barreto). Bug fixes and improved efficiency (with some
compilers).This code was written in order to clarify the mathematical
description, and to run the statistical test. Without modification, it
should not be used to encrypt files, or for any other application.Test
values (as required by NIST) . You can download information on the test
vector format here .A program that illustrates the File Encryption, Data
Encryption, personal Encryption, Message Encryption, E-Mail Encryption,
E mail Encryption, email encryption, working of Rijndael, by Jose de
Jesus Angel.ther Picture Encryption. Implementations C code from Brian
Gladman's page. A code size optimized version by Robert G. Durnal. Also
available here. (Now also available for people outside the USA and Canada.)Geoffrey
Keating's page has a fast implementation on the Motorola 6805. Mike Scott's
implementation. An 80186 assembly Picture Encryption. implementation,
written by Rafael R. Sevilla (updated on August 21, 2000). The v2.4 code,
rewritten as a compact-easy-to-use C++ class by Szymon Stefanek. Ada
95 code , by Michael Yoder. NIST's pages have links to more implementations
on various platforms. It's in Wei Dai's Crypto++ library .An implementation
in Oberon-2, by Paulo Barreto. A JAVA servlet implementation, by Cass
Crockatt. A Visual Basic implementation, by P. Fresle (updated on April
20, 2001).An Emacs Lisp implementation, by Simon Jozefsson. An implementation
in C++, by Gerhard Wesp. (GNU Lesser Public License). It's in the Catacomb
crypto library, by Mark Wooding.A free Delphi implementation by Eldos
A Perl module by Rafael R. Sevilla. A Matlab implementation by J.J. Buchholz.
A port to the Symbian OS.Python code AES Lib for Palm OS by Stuart Eichert.
C by Christophe Devine. An Atmal implementation by Sung Ha Kim. (Note
that the documentation uses File Encryption, Data Encryption, personal
Encryption, Message Encryption, E-Mail Encryption, E mail Encryption,
email encryption, the old names for the subroutines, which are different
from the names in the FIPS.)Andre Barbosa implemented Rijndael in Actionscript.
You can download the code and test it. Jose Luis Gomez Pardo implemented
Rijndael in Mathematica. Available here. Rijndael is used in the digital
lecture board, developed at the university of Mannheim. It is also used
in a freeware file protection tool called FIVE.More information and analysis
The NIST AES site contains a multitude of reports covering more topics
of the AES/Rijndael than we would have thought possible. Prof. J. von
zur Gathen organized two Rijndael seminars at the university of Paderborn
(Germany). A lot of interesting material was developed, and File Encryption,
Data Encryption, personal Encryption, Message Encryption, E-Mail Encryption,
E mail Encryption, email encryption, is available here. Rijndael FAQ
How is that pronounced If you're Dutch, Flemish, Indonesian, Surinamer
or South-African, it's pronounced like you think it should be. Otherwise,
you could pronounce it like "Reign Dahl", "Rain Doll", "Rhine Dahl".
We're not picky. As long as you make it sound different from "Region
Deal".Why did you Picture Encryption. choose this name Because we were
both fed up with people mutilating the pronunciation of the names "Daemen" and "Rijmen".
(There are two messages in this answer.) Can't you give it another name
? (Propose it as a tweak Dutch is a wonderful language. Currently we
are debating about the names "Herfstvrucht", "Angstschreeuw" and "Koeieuier".
Other suggestions are welcome of course. Derek Brown, Toronto, Ontario,
Canada, proposes "bob".Rubberhose transparently and deniably encrypts
disk data, minimising the effectiveness of warrants, coersive interrogations
and other compulsive mechanims, such as U.K RIP legislation. Rubberhose
differs from conventional disk encryption systems in that it has an advanced
modular architecture, self-test suite, is more secure, portable, utilises
information hiding (steganography / deniable cryptography), works with
any file system and has source freely available.Using linux, putting
a deniable file system on a USB memory device, leaving no trace in the
host should not be tricky as an initial problem. FUSE (the user land
file system) would seem to be a likely candidate.The more difficult problem
is the secondary one. How can I be sure that no traces of the data in
the deniable filesystem remain in the host after I remove the USB device?
There are a few obvious areas of concern - swap file, automatically written
backups (generated by editors, etc.) that might be written in the users
home directory in a resident file system, etc.One way to start might
be to chroot to a normal file system on the USB device, and then mount
the deniable system also on that device. This would leave swap and possibly
incriminating entries in log files. Swapping could be disabled as well
as loggingI've been using this product, http://www.truecrypt.org/, it
has two levels of 'plausible deniability'. Using hidden volumes and volumes
are not identifiable as truecrypt volumes, just random data.If the mere
existance of encrypted data can is some places and or circumstances be
taken as incriminating evidence, then surely the existance of the rubberhost
kernel modules might also be hazardous.If you are only going to use the
rubberhose data on a small set of known machines, the the modules could
be installable, which would solve the problem.On the other hand, following
up on the USB idea, the advantage here is that one might, for instance,
slip into a random internet cafe, do whatever, and leave. This disallows
installable kernel modules. It is true that at this time, I doubt that
internet cafes will have linux - especially linux with FUSE support,
but this may be changing.Overall, a complete linux running in userland
stored on USB may be the more practical approach.Until the popular operating
systems put random noise onto empty disk sectors instead of zeros, all
of these methods will still point to the use of encryption. I have used
truecrypt and like it for some applications. But I don't think I would
recomend it to someone who would be jailed if they were found to be in
possesion of encrypted data.Later versions of FreeBSD provides native
support for an encrypted filesystem, along with some additional steganography
which, supposedly, can masquerade the encrypted filesystem as unencrypted
data.It is all done within the "Geom Based Disk Encryption" (gbde)-framework,
described here:There is a device that kinda does this. It's called a
Blackdog. It's about the size of a credit card, 10 cards thick. It has
a fingerprint reader, and an PPC/FPGA running linux. That is, processes
run outside the OS of the "host PC". It's a weird device that isn't very
secure, but it's a good start and great idea.Basically, you create an "outer" encrypted
volume (we'll call it 'O'). You put a few files in it that aren't really
all that important, and protect O with a passphrase.Then, using some
of the free space on O (which is random bits), you create an "inner" volume
('I'), which *looks* like random bits. Nothing about O gives any clue
as to the existence of I -- you have to know I is there to even attempt
to use it.The idea is that if someone captures your filesystem, you might
be forced under duress to give up the passphrase for O, but could still
keep the existence of I hidden.In principle, however, the fact that TrueCrypt
has this function is public knowledge, and therefore keeping I a secret
isn't trivial. If detained by "legal" police, you might have deniability
-- it would be hard for them to prove you have an I volume.If detained
by the secret police, however, one would be questioned about the use
of this feature, and such (hopefully hypothetical) illegal organizations
are willing and able to "extract" such information (e.g. through the
use of sodium pentathol).Jetico's BestCrypt product also offers hidden
containers. I haven't tried using them though, I've always been afraid
of getting my drives confused and writing to the container holding the
hidden container and accidently damaging/destroying the hidden container
and its contents.Indeed, invisibility is key.Just like the 'ZoneAlarm'
method. Why protect a 'known computer'? Everything can be compromised
(in the end with bruteforce)Simply make the computer invisible.because
things that do not exist cannot be comprommised.Rubberhose was always
clunky, but the major feature it had, which TrueCrypt doesn't, is the
unprovability that there are any further layers of encryption. As physical
torture becomes less useful if the victim can plausibly deny any further
layers...Thus the name Rubberhose When everyone has security tools, then
having security tools won't mark you as a criminal.