Friday, December 21, 2007

FFMPEG

FFmpeg is a collection of software libraries that can record, convert and stream digital audio and video in numerous formats. It includes libavcodec, an audio/video codec library used by several other projects, and libavformat, an audio/video container mux and demux library. The name of the project comes from the MPEG video standards group, together with "FF" for "fast forward".[1]

The project was started by Fabrice Bellard (using the pseudonym “Gerard Lantau”), and is now maintained by Michael Niedermayer. Many FFmpeg developers are also part of the MPlayer project, and FFmpeg is hosted at the MPlayer project server.

FFmpeg is developed under Linux, but it can be compiled under most operating systems, including Microsoft Windows. There are no releases. Instead, FFmpeg developers recommend using the latest Subversion snapshot as development maintains a constantly stable trunk.[citation needed] Released under the GNU Lesser General Public License or GNU General Public License (depending on which sub-libraries one would include), FFmpeg is free software.

COMPONENTS:-
The project is made of several components:

* ffmpeg is a command line tool to convert one video file format to another. It also supports grabbing and encoding in real time from a TV card.
* ffserver is an HTTP (RTSP is being developed) multimedia streaming server for live broadcasts. Time shifting of live broadcast is also supported.
* ffplay is a simple media player based on SDL and on the FFmpeg libraries.
* libavcodec is a library containing all the FFmpeg audio/video encoders and decoders. Most codecs were developed from scratch to ensure best performance and high code reusability.
* libavformat is a library containing demuxers and muxers for audio/video container formats.
* libavutil is a helper library containing routines common to different parts of FFmpeg.
* libpostproc is a library containing video postprocessing routines.
* libswscale is a library containing video image scaling routines.

CODECS AND FORMAT SUPPORTED:-
* ATRAC3[2]
* H.261,[2] H.263[2] and h.264/MPEG-4 AVC[2]
* Indeo 2 and 3[2]
* QDesign Music Codec 2, used by many QuickTime movies prior to QuickTime 7.
* Sorenson 3 Codec used by many QuickTime movies
* Theora (together with Vorbis makes a base for the .ogg format)
* Truespeech
* TXD[3]
* VP5[2] and VP6[2]
* Vorbis
* Windows Media Audio
* Some Windows Media Video codecs, including WMV1, WMV2 and WMV3

The default MPEG-4 codec used by FFmpeg for encoding has the FourCC of FMP4.

FFMPEG

FFmpeg is a collection of software libraries that can record, convert and stream digital audio and video in numerous formats. It includes libavcodec, an audio/video codec library used by several other projects, and libavformat, an audio/video container mux and demux library. The name of the project comes from the MPEG video standards group, together with "FF" for "fast forward".[1]

The project was started by Fabrice Bellard (using the pseudonym “Gerard Lantau”), and is now maintained by Michael Niedermayer. Many FFmpeg developers are also part of the MPlayer project, and FFmpeg is hosted at the MPlayer project server.

FFmpeg is developed under Linux, but it can be compiled under most operating systems, including Microsoft Windows. There are no releases. Instead, FFmpeg developers recommend using the latest Subversion snapshot as development maintains a constantly stable trunk.[citation needed] Released under the GNU Lesser General Public License or GNU General Public License (depending on which sub-libraries one would include), FFmpeg is free software.

COMPONENTS:-
The project is made of several components:

* ffmpeg is a command line tool to convert one video file format to another. It also supports grabbing and encoding in real time from a TV card.
* ffserver is an HTTP (RTSP is being developed) multimedia streaming server for live broadcasts. Time shifting of live broadcast is also supported.
* ffplay is a simple media player based on SDL and on the FFmpeg libraries.
* libavcodec is a library containing all the FFmpeg audio/video encoders and decoders. Most codecs were developed from scratch to ensure best performance and high code reusability.
* libavformat is a library containing demuxers and muxers for audio/video container formats.
* libavutil is a helper library containing routines common to different parts of FFmpeg.
* libpostproc is a library containing video postprocessing routines.
* libswscale is a library containing video image scaling routines.

CODECS AND FORMAT SUPPORTED:-
* ATRAC3[2]
* H.261,[2] H.263[2] and h.264/MPEG-4 AVC[2]
* Indeo 2 and 3[2]
* QDesign Music Codec 2, used by many QuickTime movies prior to QuickTime 7.
* Sorenson 3 Codec used by many QuickTime movies
* Theora (together with Vorbis makes a base for the .ogg format)
* Truespeech
* TXD[3]
* VP5[2] and VP6[2]
* Vorbis
* Windows Media Audio
* Some Windows Media Video codecs, including WMV1, WMV2 and WMV3

The default MPEG-4 codec used by FFmpeg for encoding has the FourCC of FMP4.

FFMPEG

FFmpeg is a collection of software libraries that can record, convert and stream digital audio and video in numerous formats. It includes libavcodec, an audio/video codec library used by several other projects, and libavformat, an audio/video container mux and demux library. The name of the project comes from the MPEG video standards group, together with "FF" for "fast forward".[1]

The project was started by Fabrice Bellard (using the pseudonym “Gerard Lantau”), and is now maintained by Michael Niedermayer. Many FFmpeg developers are also part of the MPlayer project, and FFmpeg is hosted at the MPlayer project server.

FFmpeg is developed under Linux, but it can be compiled under most operating systems, including Microsoft Windows. There are no releases. Instead, FFmpeg developers recommend using the latest Subversion snapshot as development maintains a constantly stable trunk.[citation needed] Released under the GNU Lesser General Public License or GNU General Public License (depending on which sub-libraries one would include), FFmpeg is free software.

COMPONENTS:-
The project is made of several components:

* ffmpeg is a command line tool to convert one video file format to another. It also supports grabbing and encoding in real time from a TV card.
* ffserver is an HTTP (RTSP is being developed) multimedia streaming server for live broadcasts. Time shifting of live broadcast is also supported.
* ffplay is a simple media player based on SDL and on the FFmpeg libraries.
* libavcodec is a library containing all the FFmpeg audio/video encoders and decoders. Most codecs were developed from scratch to ensure best performance and high code reusability.
* libavformat is a library containing demuxers and muxers for audio/video container formats.
* libavutil is a helper library containing routines common to different parts of FFmpeg.
* libpostproc is a library containing video postprocessing routines.
* libswscale is a library containing video image scaling routines.

CODECS AND FORMAT SUPPORTED:-
* ATRAC3[2]
* H.261,[2] H.263[2] and h.264/MPEG-4 AVC[2]
* Indeo 2 and 3[2]
* QDesign Music Codec 2, used by many QuickTime movies prior to QuickTime 7.
* Sorenson 3 Codec used by many QuickTime movies
* Theora (together with Vorbis makes a base for the .ogg format)
* Truespeech
* TXD[3]
* VP5[2] and VP6[2]
* Vorbis
* Windows Media Audio
* Some Windows Media Video codecs, including WMV1, WMV2 and WMV3

The default MPEG-4 codec used by FFmpeg for encoding has the FourCC of FMP4.

FFMPEG

FFmpeg is a collection of software libraries that can record, convert and stream digital audio and video in numerous formats. It includes libavcodec, an audio/video codec library used by several other projects, and libavformat, an audio/video container mux and demux library. The name of the project comes from the MPEG video standards group, together with "FF" for "fast forward".[1]

The project was started by Fabrice Bellard (using the pseudonym “Gerard Lantau”), and is now maintained by Michael Niedermayer. Many FFmpeg developers are also part of the MPlayer project, and FFmpeg is hosted at the MPlayer project server.

FFmpeg is developed under Linux, but it can be compiled under most operating systems, including Microsoft Windows. There are no releases. Instead, FFmpeg developers recommend using the latest Subversion snapshot as development maintains a constantly stable trunk.[citation needed] Released under the GNU Lesser General Public License or GNU General Public License (depending on which sub-libraries one would include), FFmpeg is free software.

COMPONENTS:-
The project is made of several components:

* ffmpeg is a command line tool to convert one video file format to another. It also supports grabbing and encoding in real time from a TV card.
* ffserver is an HTTP (RTSP is being developed) multimedia streaming server for live broadcasts. Time shifting of live broadcast is also supported.
* ffplay is a simple media player based on SDL and on the FFmpeg libraries.
* libavcodec is a library containing all the FFmpeg audio/video encoders and decoders. Most codecs were developed from scratch to ensure best performance and high code reusability.
* libavformat is a library containing demuxers and muxers for audio/video container formats.
* libavutil is a helper library containing routines common to different parts of FFmpeg.
* libpostproc is a library containing video postprocessing routines.
* libswscale is a library containing video image scaling routines.

CODECS AND FORMAT SUPPORTED:-
* ATRAC3[2]
* H.261,[2] H.263[2] and h.264/MPEG-4 AVC[2]
* Indeo 2 and 3[2]
* QDesign Music Codec 2, used by many QuickTime movies prior to QuickTime 7.
* Sorenson 3 Codec used by many QuickTime movies
* Theora (together with Vorbis makes a base for the .ogg format)
* Truespeech
* TXD[3]
* VP5[2] and VP6[2]
* Vorbis
* Windows Media Audio
* Some Windows Media Video codecs, including WMV1, WMV2 and WMV3

The default MPEG-4 codec used by FFmpeg for encoding has the FourCC of FMP4.

FFMPEG

FFmpeg is a collection of software libraries that can record, convert and stream digital audio and video in numerous formats. It includes libavcodec, an audio/video codec library used by several other projects, and libavformat, an audio/video container mux and demux library. The name of the project comes from the MPEG video standards group, together with "FF" for "fast forward".[1]

The project was started by Fabrice Bellard (using the pseudonym “Gerard Lantau”), and is now maintained by Michael Niedermayer. Many FFmpeg developers are also part of the MPlayer project, and FFmpeg is hosted at the MPlayer project server.

FFmpeg is developed under Linux, but it can be compiled under most operating systems, including Microsoft Windows. There are no releases. Instead, FFmpeg developers recommend using the latest Subversion snapshot as development maintains a constantly stable trunk.[citation needed] Released under the GNU Lesser General Public License or GNU General Public License (depending on which sub-libraries one would include), FFmpeg is free software.

COMPONENTS:-
The project is made of several components:

* ffmpeg is a command line tool to convert one video file format to another. It also supports grabbing and encoding in real time from a TV card.
* ffserver is an HTTP (RTSP is being developed) multimedia streaming server for live broadcasts. Time shifting of live broadcast is also supported.
* ffplay is a simple media player based on SDL and on the FFmpeg libraries.
* libavcodec is a library containing all the FFmpeg audio/video encoders and decoders. Most codecs were developed from scratch to ensure best performance and high code reusability.
* libavformat is a library containing demuxers and muxers for audio/video container formats.
* libavutil is a helper library containing routines common to different parts of FFmpeg.
* libpostproc is a library containing video postprocessing routines.
* libswscale is a library containing video image scaling routines.

CODECS AND FORMAT SUPPORTED:-
* ATRAC3[2]
* H.261,[2] H.263[2] and h.264/MPEG-4 AVC[2]
* Indeo 2 and 3[2]
* QDesign Music Codec 2, used by many QuickTime movies prior to QuickTime 7.
* Sorenson 3 Codec used by many QuickTime movies
* Theora (together with Vorbis makes a base for the .ogg format)
* Truespeech
* TXD[3]
* VP5[2] and VP6[2]
* Vorbis
* Windows Media Audio
* Some Windows Media Video codecs, including WMV1, WMV2 and WMV3

The default MPEG-4 codec used by FFmpeg for encoding has the FourCC of FMP4.

FFMPEG

FFmpeg is a collection of software libraries that can record, convert and stream digital audio and video in numerous formats. It includes libavcodec, an audio/video codec library used by several other projects, and libavformat, an audio/video container mux and demux library. The name of the project comes from the MPEG video standards group, together with "FF" for "fast forward".[1]

The project was started by Fabrice Bellard (using the pseudonym “Gerard Lantau”), and is now maintained by Michael Niedermayer. Many FFmpeg developers are also part of the MPlayer project, and FFmpeg is hosted at the MPlayer project server.

FFmpeg is developed under Linux, but it can be compiled under most operating systems, including Microsoft Windows. There are no releases. Instead, FFmpeg developers recommend using the latest Subversion snapshot as development maintains a constantly stable trunk.[citation needed] Released under the GNU Lesser General Public License or GNU General Public License (depending on which sub-libraries one would include), FFmpeg is free software.

COMPONENTS:-
The project is made of several components:

* ffmpeg is a command line tool to convert one video file format to another. It also supports grabbing and encoding in real time from a TV card.
* ffserver is an HTTP (RTSP is being developed) multimedia streaming server for live broadcasts. Time shifting of live broadcast is also supported.
* ffplay is a simple media player based on SDL and on the FFmpeg libraries.
* libavcodec is a library containing all the FFmpeg audio/video encoders and decoders. Most codecs were developed from scratch to ensure best performance and high code reusability.
* libavformat is a library containing demuxers and muxers for audio/video container formats.
* libavutil is a helper library containing routines common to different parts of FFmpeg.
* libpostproc is a library containing video postprocessing routines.
* libswscale is a library containing video image scaling routines.

CODECS AND FORMAT SUPPORTED:-
* ATRAC3[2]
* H.261,[2] H.263[2] and h.264/MPEG-4 AVC[2]
* Indeo 2 and 3[2]
* QDesign Music Codec 2, used by many QuickTime movies prior to QuickTime 7.
* Sorenson 3 Codec used by many QuickTime movies
* Theora (together with Vorbis makes a base for the .ogg format)
* Truespeech
* TXD[3]
* VP5[2] and VP6[2]
* Vorbis
* Windows Media Audio
* Some Windows Media Video codecs, including WMV1, WMV2 and WMV3

The default MPEG-4 codec used by FFmpeg for encoding has the FourCC of FMP4.

FFMPEG

FFmpeg is a collection of software libraries that can record, convert and stream digital audio and video in numerous formats. It includes libavcodec, an audio/video codec library used by several other projects, and libavformat, an audio/video container mux and demux library. The name of the project comes from the MPEG video standards group, together with "FF" for "fast forward".[1]

The project was started by Fabrice Bellard (using the pseudonym “Gerard Lantau”), and is now maintained by Michael Niedermayer. Many FFmpeg developers are also part of the MPlayer project, and FFmpeg is hosted at the MPlayer project server.

FFmpeg is developed under Linux, but it can be compiled under most operating systems, including Microsoft Windows. There are no releases. Instead, FFmpeg developers recommend using the latest Subversion snapshot as development maintains a constantly stable trunk.[citation needed] Released under the GNU Lesser General Public License or GNU General Public License (depending on which sub-libraries one would include), FFmpeg is free software.

COMPONENTS:-
The project is made of several components:

* ffmpeg is a command line tool to convert one video file format to another. It also supports grabbing and encoding in real time from a TV card.
* ffserver is an HTTP (RTSP is being developed) multimedia streaming server for live broadcasts. Time shifting of live broadcast is also supported.
* ffplay is a simple media player based on SDL and on the FFmpeg libraries.
* libavcodec is a library containing all the FFmpeg audio/video encoders and decoders. Most codecs were developed from scratch to ensure best performance and high code reusability.
* libavformat is a library containing demuxers and muxers for audio/video container formats.
* libavutil is a helper library containing routines common to different parts of FFmpeg.
* libpostproc is a library containing video postprocessing routines.
* libswscale is a library containing video image scaling routines.

CODECS AND FORMAT SUPPORTED:-
* ATRAC3[2]
* H.261,[2] H.263[2] and h.264/MPEG-4 AVC[2]
* Indeo 2 and 3[2]
* QDesign Music Codec 2, used by many QuickTime movies prior to QuickTime 7.
* Sorenson 3 Codec used by many QuickTime movies
* Theora (together with Vorbis makes a base for the .ogg format)
* Truespeech
* TXD[3]
* VP5[2] and VP6[2]
* Vorbis
* Windows Media Audio
* Some Windows Media Video codecs, including WMV1, WMV2 and WMV3

The default MPEG-4 codec used by FFmpeg for encoding has the FourCC of FMP4.

FFMPEG

FFmpeg is a collection of software libraries that can record, convert and stream digital audio and video in numerous formats. It includes libavcodec, an audio/video codec library used by several other projects, and libavformat, an audio/video container mux and demux library. The name of the project comes from the MPEG video standards group, together with "FF" for "fast forward".[1]

The project was started by Fabrice Bellard (using the pseudonym “Gerard Lantau”), and is now maintained by Michael Niedermayer. Many FFmpeg developers are also part of the MPlayer project, and FFmpeg is hosted at the MPlayer project server.

FFmpeg is developed under Linux, but it can be compiled under most operating systems, including Microsoft Windows. There are no releases. Instead, FFmpeg developers recommend using the latest Subversion snapshot as development maintains a constantly stable trunk.[citation needed] Released under the GNU Lesser General Public License or GNU General Public License (depending on which sub-libraries one would include), FFmpeg is free software.

COMPONENTS:-
The project is made of several components:

* ffmpeg is a command line tool to convert one video file format to another. It also supports grabbing and encoding in real time from a TV card.
* ffserver is an HTTP (RTSP is being developed) multimedia streaming server for live broadcasts. Time shifting of live broadcast is also supported.
* ffplay is a simple media player based on SDL and on the FFmpeg libraries.
* libavcodec is a library containing all the FFmpeg audio/video encoders and decoders. Most codecs were developed from scratch to ensure best performance and high code reusability.
* libavformat is a library containing demuxers and muxers for audio/video container formats.
* libavutil is a helper library containing routines common to different parts of FFmpeg.
* libpostproc is a library containing video postprocessing routines.
* libswscale is a library containing video image scaling routines.

CODECS AND FORMAT SUPPORTED:-
* ATRAC3[2]
* H.261,[2] H.263[2] and h.264/MPEG-4 AVC[2]
* Indeo 2 and 3[2]
* QDesign Music Codec 2, used by many QuickTime movies prior to QuickTime 7.
* Sorenson 3 Codec used by many QuickTime movies
* Theora (together with Vorbis makes a base for the .ogg format)
* Truespeech
* TXD[3]
* VP5[2] and VP6[2]
* Vorbis
* Windows Media Audio
* Some Windows Media Video codecs, including WMV1, WMV2 and WMV3

The default MPEG-4 codec used by FFmpeg for encoding has the FourCC of FMP4.

FFMPEG

FFmpeg is a collection of software libraries that can record, convert and stream digital audio and video in numerous formats. It includes libavcodec, an audio/video codec library used by several other projects, and libavformat, an audio/video container mux and demux library. The name of the project comes from the MPEG video standards group, together with "FF" for "fast forward".[1]

The project was started by Fabrice Bellard (using the pseudonym “Gerard Lantau”), and is now maintained by Michael Niedermayer. Many FFmpeg developers are also part of the MPlayer project, and FFmpeg is hosted at the MPlayer project server.

FFmpeg is developed under Linux, but it can be compiled under most operating systems, including Microsoft Windows. There are no releases. Instead, FFmpeg developers recommend using the latest Subversion snapshot as development maintains a constantly stable trunk.[citation needed] Released under the GNU Lesser General Public License or GNU General Public License (depending on which sub-libraries one would include), FFmpeg is free software.

COMPONENTS:-
The project is made of several components:

* ffmpeg is a command line tool to convert one video file format to another. It also supports grabbing and encoding in real time from a TV card.
* ffserver is an HTTP (RTSP is being developed) multimedia streaming server for live broadcasts. Time shifting of live broadcast is also supported.
* ffplay is a simple media player based on SDL and on the FFmpeg libraries.
* libavcodec is a library containing all the FFmpeg audio/video encoders and decoders. Most codecs were developed from scratch to ensure best performance and high code reusability.
* libavformat is a library containing demuxers and muxers for audio/video container formats.
* libavutil is a helper library containing routines common to different parts of FFmpeg.
* libpostproc is a library containing video postprocessing routines.
* libswscale is a library containing video image scaling routines.

CODECS AND FORMAT SUPPORTED:-
* ATRAC3[2]
* H.261,[2] H.263[2] and h.264/MPEG-4 AVC[2]
* Indeo 2 and 3[2]
* QDesign Music Codec 2, used by many QuickTime movies prior to QuickTime 7.
* Sorenson 3 Codec used by many QuickTime movies
* Theora (together with Vorbis makes a base for the .ogg format)
* Truespeech
* TXD[3]
* VP5[2] and VP6[2]
* Vorbis
* Windows Media Audio
* Some Windows Media Video codecs, including WMV1, WMV2 and WMV3

The default MPEG-4 codec used by FFmpeg for encoding has the FourCC of FMP4.

FFMPEG

FFmpeg is a collection of software libraries that can record, convert and stream digital audio and video in numerous formats. It includes libavcodec, an audio/video codec library used by several other projects, and libavformat, an audio/video container mux and demux library. The name of the project comes from the MPEG video standards group, together with "FF" for "fast forward".[1]

The project was started by Fabrice Bellard (using the pseudonym “Gerard Lantau”), and is now maintained by Michael Niedermayer. Many FFmpeg developers are also part of the MPlayer project, and FFmpeg is hosted at the MPlayer project server.

FFmpeg is developed under Linux, but it can be compiled under most operating systems, including Microsoft Windows. There are no releases. Instead, FFmpeg developers recommend using the latest Subversion snapshot as development maintains a constantly stable trunk.[citation needed] Released under the GNU Lesser General Public License or GNU General Public License (depending on which sub-libraries one would include), FFmpeg is free software.

COMPONENTS:-
The project is made of several components:

* ffmpeg is a command line tool to convert one video file format to another. It also supports grabbing and encoding in real time from a TV card.
* ffserver is an HTTP (RTSP is being developed) multimedia streaming server for live broadcasts. Time shifting of live broadcast is also supported.
* ffplay is a simple media player based on SDL and on the FFmpeg libraries.
* libavcodec is a library containing all the FFmpeg audio/video encoders and decoders. Most codecs were developed from scratch to ensure best performance and high code reusability.
* libavformat is a library containing demuxers and muxers for audio/video container formats.
* libavutil is a helper library containing routines common to different parts of FFmpeg.
* libpostproc is a library containing video postprocessing routines.
* libswscale is a library containing video image scaling routines.

CODECS AND FORMAT SUPPORTED:-
* ATRAC3[2]
* H.261,[2] H.263[2] and h.264/MPEG-4 AVC[2]
* Indeo 2 and 3[2]
* QDesign Music Codec 2, used by many QuickTime movies prior to QuickTime 7.
* Sorenson 3 Codec used by many QuickTime movies
* Theora (together with Vorbis makes a base for the .ogg format)
* Truespeech
* TXD[3]
* VP5[2] and VP6[2]
* Vorbis
* Windows Media Audio
* Some Windows Media Video codecs, including WMV1, WMV2 and WMV3

The default MPEG-4 codec used by FFmpeg for encoding has the FourCC of FMP4.

Security Tips For Business

1. You can't turn shovelware into reliable software by patching it a whole lot.
2.You shouldn't mix production systems with non-production systems.
3. You actually have to know what's going on in your networks.
4. If you run your computers with an open execution runtime model you'll always get viruses, spyware and Trojan horses.
5. You can pass laws about locking barn doors after horses have left, but it won't put the horses back in the barn.
6.Security has to be designed in, as part of a system plan for reliability, rather than bolted on afterward.

Security Tips For Business

1. You can't turn shovelware into reliable software by patching it a whole lot.
2.You shouldn't mix production systems with non-production systems.
3. You actually have to know what's going on in your networks.
4. If you run your computers with an open execution runtime model you'll always get viruses, spyware and Trojan horses.
5. You can pass laws about locking barn doors after horses have left, but it won't put the horses back in the barn.
6.Security has to be designed in, as part of a system plan for reliability, rather than bolted on afterward.

Security Tips For Business

1. You can't turn shovelware into reliable software by patching it a whole lot.
2.You shouldn't mix production systems with non-production systems.
3. You actually have to know what's going on in your networks.
4. If you run your computers with an open execution runtime model you'll always get viruses, spyware and Trojan horses.
5. You can pass laws about locking barn doors after horses have left, but it won't put the horses back in the barn.
6.Security has to be designed in, as part of a system plan for reliability, rather than bolted on afterward.

Security Tips For Business

1. You can't turn shovelware into reliable software by patching it a whole lot.
2.You shouldn't mix production systems with non-production systems.
3. You actually have to know what's going on in your networks.
4. If you run your computers with an open execution runtime model you'll always get viruses, spyware and Trojan horses.
5. You can pass laws about locking barn doors after horses have left, but it won't put the horses back in the barn.
6.Security has to be designed in, as part of a system plan for reliability, rather than bolted on afterward.

Security Tips For Business

1. You can't turn shovelware into reliable software by patching it a whole lot.
2.You shouldn't mix production systems with non-production systems.
3. You actually have to know what's going on in your networks.
4. If you run your computers with an open execution runtime model you'll always get viruses, spyware and Trojan horses.
5. You can pass laws about locking barn doors after horses have left, but it won't put the horses back in the barn.
6.Security has to be designed in, as part of a system plan for reliability, rather than bolted on afterward.

Security Tips For Business

1. You can't turn shovelware into reliable software by patching it a whole lot.
2.You shouldn't mix production systems with non-production systems.
3. You actually have to know what's going on in your networks.
4. If you run your computers with an open execution runtime model you'll always get viruses, spyware and Trojan horses.
5. You can pass laws about locking barn doors after horses have left, but it won't put the horses back in the barn.
6.Security has to be designed in, as part of a system plan for reliability, rather than bolted on afterward.

Security Tips For Business

1. You can't turn shovelware into reliable software by patching it a whole lot.
2.You shouldn't mix production systems with non-production systems.
3. You actually have to know what's going on in your networks.
4. If you run your computers with an open execution runtime model you'll always get viruses, spyware and Trojan horses.
5. You can pass laws about locking barn doors after horses have left, but it won't put the horses back in the barn.
6.Security has to be designed in, as part of a system plan for reliability, rather than bolted on afterward.

Security Tips For Business

1. You can't turn shovelware into reliable software by patching it a whole lot.
2.You shouldn't mix production systems with non-production systems.
3. You actually have to know what's going on in your networks.
4. If you run your computers with an open execution runtime model you'll always get viruses, spyware and Trojan horses.
5. You can pass laws about locking barn doors after horses have left, but it won't put the horses back in the barn.
6.Security has to be designed in, as part of a system plan for reliability, rather than bolted on afterward.

Security Tips For Business

1. You can't turn shovelware into reliable software by patching it a whole lot.
2.You shouldn't mix production systems with non-production systems.
3. You actually have to know what's going on in your networks.
4. If you run your computers with an open execution runtime model you'll always get viruses, spyware and Trojan horses.
5. You can pass laws about locking barn doors after horses have left, but it won't put the horses back in the barn.
6.Security has to be designed in, as part of a system plan for reliability, rather than bolted on afterward.

Security Tips For Business

1. You can't turn shovelware into reliable software by patching it a whole lot.
2.You shouldn't mix production systems with non-production systems.
3. You actually have to know what's going on in your networks.
4. If you run your computers with an open execution runtime model you'll always get viruses, spyware and Trojan horses.
5. You can pass laws about locking barn doors after horses have left, but it won't put the horses back in the barn.
6.Security has to be designed in, as part of a system plan for reliability, rather than bolted on afterward.

Security Reminder

This week, the orkut team discovered that a user had exploited a bug in our scrapbook feature. As a result, many of you likely received scraps from friends of yours that they actually didn't send, and friends may have received scraps that appeared to come from you.

The orkut team responded quickly, and worked late into the night to fix the underlying issue and contain the spread of these scraps.

We believe that this action has been effectively stopped and you should no longer receive any more of these unintended messages. We appreciate your understanding in this case and hope that this did not create too much of an inconvenience for you or your fellow orkut friends.

-Abhi

Security Reminder

This week, the orkut team discovered that a user had exploited a bug in our scrapbook feature. As a result, many of you likely received scraps from friends of yours that they actually didn't send, and friends may have received scraps that appeared to come from you.

The orkut team responded quickly, and worked late into the night to fix the underlying issue and contain the spread of these scraps.

We believe that this action has been effectively stopped and you should no longer receive any more of these unintended messages. We appreciate your understanding in this case and hope that this did not create too much of an inconvenience for you or your fellow orkut friends.

-Abhi

Security Reminder

This week, the orkut team discovered that a user had exploited a bug in our scrapbook feature. As a result, many of you likely received scraps from friends of yours that they actually didn't send, and friends may have received scraps that appeared to come from you.

The orkut team responded quickly, and worked late into the night to fix the underlying issue and contain the spread of these scraps.

We believe that this action has been effectively stopped and you should no longer receive any more of these unintended messages. We appreciate your understanding in this case and hope that this did not create too much of an inconvenience for you or your fellow orkut friends.

-Abhi

Security Reminder

This week, the orkut team discovered that a user had exploited a bug in our scrapbook feature. As a result, many of you likely received scraps from friends of yours that they actually didn't send, and friends may have received scraps that appeared to come from you.

The orkut team responded quickly, and worked late into the night to fix the underlying issue and contain the spread of these scraps.

We believe that this action has been effectively stopped and you should no longer receive any more of these unintended messages. We appreciate your understanding in this case and hope that this did not create too much of an inconvenience for you or your fellow orkut friends.

-Abhi

Security Reminder

This week, the orkut team discovered that a user had exploited a bug in our scrapbook feature. As a result, many of you likely received scraps from friends of yours that they actually didn't send, and friends may have received scraps that appeared to come from you.

The orkut team responded quickly, and worked late into the night to fix the underlying issue and contain the spread of these scraps.

We believe that this action has been effectively stopped and you should no longer receive any more of these unintended messages. We appreciate your understanding in this case and hope that this did not create too much of an inconvenience for you or your fellow orkut friends.

-Abhi

Security Reminder

This week, the orkut team discovered that a user had exploited a bug in our scrapbook feature. As a result, many of you likely received scraps from friends of yours that they actually didn't send, and friends may have received scraps that appeared to come from you.

The orkut team responded quickly, and worked late into the night to fix the underlying issue and contain the spread of these scraps.

We believe that this action has been effectively stopped and you should no longer receive any more of these unintended messages. We appreciate your understanding in this case and hope that this did not create too much of an inconvenience for you or your fellow orkut friends.

-Abhi

Security Reminder

This week, the orkut team discovered that a user had exploited a bug in our scrapbook feature. As a result, many of you likely received scraps from friends of yours that they actually didn't send, and friends may have received scraps that appeared to come from you.

The orkut team responded quickly, and worked late into the night to fix the underlying issue and contain the spread of these scraps.

We believe that this action has been effectively stopped and you should no longer receive any more of these unintended messages. We appreciate your understanding in this case and hope that this did not create too much of an inconvenience for you or your fellow orkut friends.

-Abhi

Security Reminder

This week, the orkut team discovered that a user had exploited a bug in our scrapbook feature. As a result, many of you likely received scraps from friends of yours that they actually didn't send, and friends may have received scraps that appeared to come from you.

The orkut team responded quickly, and worked late into the night to fix the underlying issue and contain the spread of these scraps.

We believe that this action has been effectively stopped and you should no longer receive any more of these unintended messages. We appreciate your understanding in this case and hope that this did not create too much of an inconvenience for you or your fellow orkut friends.

-Abhi

Security Reminder

This week, the orkut team discovered that a user had exploited a bug in our scrapbook feature. As a result, many of you likely received scraps from friends of yours that they actually didn't send, and friends may have received scraps that appeared to come from you.

The orkut team responded quickly, and worked late into the night to fix the underlying issue and contain the spread of these scraps.

We believe that this action has been effectively stopped and you should no longer receive any more of these unintended messages. We appreciate your understanding in this case and hope that this did not create too much of an inconvenience for you or your fellow orkut friends.

-Abhi

Security Reminder

This week, the orkut team discovered that a user had exploited a bug in our scrapbook feature. As a result, many of you likely received scraps from friends of yours that they actually didn't send, and friends may have received scraps that appeared to come from you.

The orkut team responded quickly, and worked late into the night to fix the underlying issue and contain the spread of these scraps.

We believe that this action has been effectively stopped and you should no longer receive any more of these unintended messages. We appreciate your understanding in this case and hope that this did not create too much of an inconvenience for you or your fellow orkut friends.

-Abhi

Security Rules Employers Like To Break

1. Copying confidential information onto a USB memory stick: Eighty-seven percent of respondents believe their company’s policy forbids it, yet 51 percent say they do it anyway.

2. Accessing web-based e-mail accounts from a workplace computer: Forty-five percent of those surveyed use webmail at work; 74 percent say there is no stated policy that forbids it.

3. Losing a portable data-bearing device: Thirty-nine percent of respondents say they have lost or misplaced such a device, and 72 percent of them did not report the lost device immediately.

4. Downloading personal software onto a company computer: Sixty percent of respondents say there is no stated policy that forbids downloading personal software, a practice that 45 percent of respondents admit to.

5. Sending workplace documents as an attachment in e-mail: Thirty-three percent of respondents send work documents as attachments, and 48 percent aren’t even sure whether or not that violates policy.

6. Disabling security and firewall settings: Eighty percent of those surveyed don’t know whether disabling security is against policy; 17 percent of respondents do it.

7. Sharing passwords with co-workers: Sixty-seven percent say the company’s policy forbids sharing passwords, but 46 percent of them do it anyway.


-Abhi

Security Rules Employers Like To Break

1. Copying confidential information onto a USB memory stick: Eighty-seven percent of respondents believe their company’s policy forbids it, yet 51 percent say they do it anyway.

2. Accessing web-based e-mail accounts from a workplace computer: Forty-five percent of those surveyed use webmail at work; 74 percent say there is no stated policy that forbids it.

3. Losing a portable data-bearing device: Thirty-nine percent of respondents say they have lost or misplaced such a device, and 72 percent of them did not report the lost device immediately.

4. Downloading personal software onto a company computer: Sixty percent of respondents say there is no stated policy that forbids downloading personal software, a practice that 45 percent of respondents admit to.

5. Sending workplace documents as an attachment in e-mail: Thirty-three percent of respondents send work documents as attachments, and 48 percent aren’t even sure whether or not that violates policy.

6. Disabling security and firewall settings: Eighty percent of those surveyed don’t know whether disabling security is against policy; 17 percent of respondents do it.

7. Sharing passwords with co-workers: Sixty-seven percent say the company’s policy forbids sharing passwords, but 46 percent of them do it anyway.


-Abhi

Security Rules Employers Like To Break

1. Copying confidential information onto a USB memory stick: Eighty-seven percent of respondents believe their company’s policy forbids it, yet 51 percent say they do it anyway.

2. Accessing web-based e-mail accounts from a workplace computer: Forty-five percent of those surveyed use webmail at work; 74 percent say there is no stated policy that forbids it.

3. Losing a portable data-bearing device: Thirty-nine percent of respondents say they have lost or misplaced such a device, and 72 percent of them did not report the lost device immediately.

4. Downloading personal software onto a company computer: Sixty percent of respondents say there is no stated policy that forbids downloading personal software, a practice that 45 percent of respondents admit to.

5. Sending workplace documents as an attachment in e-mail: Thirty-three percent of respondents send work documents as attachments, and 48 percent aren’t even sure whether or not that violates policy.

6. Disabling security and firewall settings: Eighty percent of those surveyed don’t know whether disabling security is against policy; 17 percent of respondents do it.

7. Sharing passwords with co-workers: Sixty-seven percent say the company’s policy forbids sharing passwords, but 46 percent of them do it anyway.


-Abhi

Security Rules Employers Like To Break

1. Copying confidential information onto a USB memory stick: Eighty-seven percent of respondents believe their company’s policy forbids it, yet 51 percent say they do it anyway.

2. Accessing web-based e-mail accounts from a workplace computer: Forty-five percent of those surveyed use webmail at work; 74 percent say there is no stated policy that forbids it.

3. Losing a portable data-bearing device: Thirty-nine percent of respondents say they have lost or misplaced such a device, and 72 percent of them did not report the lost device immediately.

4. Downloading personal software onto a company computer: Sixty percent of respondents say there is no stated policy that forbids downloading personal software, a practice that 45 percent of respondents admit to.

5. Sending workplace documents as an attachment in e-mail: Thirty-three percent of respondents send work documents as attachments, and 48 percent aren’t even sure whether or not that violates policy.

6. Disabling security and firewall settings: Eighty percent of those surveyed don’t know whether disabling security is against policy; 17 percent of respondents do it.

7. Sharing passwords with co-workers: Sixty-seven percent say the company’s policy forbids sharing passwords, but 46 percent of them do it anyway.


-Abhi

Security Rules Employers Like To Break

1. Copying confidential information onto a USB memory stick: Eighty-seven percent of respondents believe their company’s policy forbids it, yet 51 percent say they do it anyway.

2. Accessing web-based e-mail accounts from a workplace computer: Forty-five percent of those surveyed use webmail at work; 74 percent say there is no stated policy that forbids it.

3. Losing a portable data-bearing device: Thirty-nine percent of respondents say they have lost or misplaced such a device, and 72 percent of them did not report the lost device immediately.

4. Downloading personal software onto a company computer: Sixty percent of respondents say there is no stated policy that forbids downloading personal software, a practice that 45 percent of respondents admit to.

5. Sending workplace documents as an attachment in e-mail: Thirty-three percent of respondents send work documents as attachments, and 48 percent aren’t even sure whether or not that violates policy.

6. Disabling security and firewall settings: Eighty percent of those surveyed don’t know whether disabling security is against policy; 17 percent of respondents do it.

7. Sharing passwords with co-workers: Sixty-seven percent say the company’s policy forbids sharing passwords, but 46 percent of them do it anyway.


-Abhi

Security Rules Employers Like To Break

1. Copying confidential information onto a USB memory stick: Eighty-seven percent of respondents believe their company’s policy forbids it, yet 51 percent say they do it anyway.

2. Accessing web-based e-mail accounts from a workplace computer: Forty-five percent of those surveyed use webmail at work; 74 percent say there is no stated policy that forbids it.

3. Losing a portable data-bearing device: Thirty-nine percent of respondents say they have lost or misplaced such a device, and 72 percent of them did not report the lost device immediately.

4. Downloading personal software onto a company computer: Sixty percent of respondents say there is no stated policy that forbids downloading personal software, a practice that 45 percent of respondents admit to.

5. Sending workplace documents as an attachment in e-mail: Thirty-three percent of respondents send work documents as attachments, and 48 percent aren’t even sure whether or not that violates policy.

6. Disabling security and firewall settings: Eighty percent of those surveyed don’t know whether disabling security is against policy; 17 percent of respondents do it.

7. Sharing passwords with co-workers: Sixty-seven percent say the company’s policy forbids sharing passwords, but 46 percent of them do it anyway.


-Abhi

Security Rules Employers Like To Break

1. Copying confidential information onto a USB memory stick: Eighty-seven percent of respondents believe their company’s policy forbids it, yet 51 percent say they do it anyway.

2. Accessing web-based e-mail accounts from a workplace computer: Forty-five percent of those surveyed use webmail at work; 74 percent say there is no stated policy that forbids it.

3. Losing a portable data-bearing device: Thirty-nine percent of respondents say they have lost or misplaced such a device, and 72 percent of them did not report the lost device immediately.

4. Downloading personal software onto a company computer: Sixty percent of respondents say there is no stated policy that forbids downloading personal software, a practice that 45 percent of respondents admit to.

5. Sending workplace documents as an attachment in e-mail: Thirty-three percent of respondents send work documents as attachments, and 48 percent aren’t even sure whether or not that violates policy.

6. Disabling security and firewall settings: Eighty percent of those surveyed don’t know whether disabling security is against policy; 17 percent of respondents do it.

7. Sharing passwords with co-workers: Sixty-seven percent say the company’s policy forbids sharing passwords, but 46 percent of them do it anyway.


-Abhi

Security Rules Employers Like To Break

1. Copying confidential information onto a USB memory stick: Eighty-seven percent of respondents believe their company’s policy forbids it, yet 51 percent say they do it anyway.

2. Accessing web-based e-mail accounts from a workplace computer: Forty-five percent of those surveyed use webmail at work; 74 percent say there is no stated policy that forbids it.

3. Losing a portable data-bearing device: Thirty-nine percent of respondents say they have lost or misplaced such a device, and 72 percent of them did not report the lost device immediately.

4. Downloading personal software onto a company computer: Sixty percent of respondents say there is no stated policy that forbids downloading personal software, a practice that 45 percent of respondents admit to.

5. Sending workplace documents as an attachment in e-mail: Thirty-three percent of respondents send work documents as attachments, and 48 percent aren’t even sure whether or not that violates policy.

6. Disabling security and firewall settings: Eighty percent of those surveyed don’t know whether disabling security is against policy; 17 percent of respondents do it.

7. Sharing passwords with co-workers: Sixty-seven percent say the company’s policy forbids sharing passwords, but 46 percent of them do it anyway.


-Abhi

Security Rules Employers Like To Break

1. Copying confidential information onto a USB memory stick: Eighty-seven percent of respondents believe their company’s policy forbids it, yet 51 percent say they do it anyway.

2. Accessing web-based e-mail accounts from a workplace computer: Forty-five percent of those surveyed use webmail at work; 74 percent say there is no stated policy that forbids it.

3. Losing a portable data-bearing device: Thirty-nine percent of respondents say they have lost or misplaced such a device, and 72 percent of them did not report the lost device immediately.

4. Downloading personal software onto a company computer: Sixty percent of respondents say there is no stated policy that forbids downloading personal software, a practice that 45 percent of respondents admit to.

5. Sending workplace documents as an attachment in e-mail: Thirty-three percent of respondents send work documents as attachments, and 48 percent aren’t even sure whether or not that violates policy.

6. Disabling security and firewall settings: Eighty percent of those surveyed don’t know whether disabling security is against policy; 17 percent of respondents do it.

7. Sharing passwords with co-workers: Sixty-seven percent say the company’s policy forbids sharing passwords, but 46 percent of them do it anyway.


-Abhi

Security Rules Employers Like To Break

1. Copying confidential information onto a USB memory stick: Eighty-seven percent of respondents believe their company’s policy forbids it, yet 51 percent say they do it anyway.

2. Accessing web-based e-mail accounts from a workplace computer: Forty-five percent of those surveyed use webmail at work; 74 percent say there is no stated policy that forbids it.

3. Losing a portable data-bearing device: Thirty-nine percent of respondents say they have lost or misplaced such a device, and 72 percent of them did not report the lost device immediately.

4. Downloading personal software onto a company computer: Sixty percent of respondents say there is no stated policy that forbids downloading personal software, a practice that 45 percent of respondents admit to.

5. Sending workplace documents as an attachment in e-mail: Thirty-three percent of respondents send work documents as attachments, and 48 percent aren’t even sure whether or not that violates policy.

6. Disabling security and firewall settings: Eighty percent of those surveyed don’t know whether disabling security is against policy; 17 percent of respondents do it.

7. Sharing passwords with co-workers: Sixty-seven percent say the company’s policy forbids sharing passwords, but 46 percent of them do it anyway.


-Abhi

Security Rules Employees Like To Break

1. Copying confidential information onto a USB memory stick: Eighty-seven percent of respondents believe their company’s policy forbids it, yet 51 percent say they do it anyway.

2. Accessing web-based e-mail accounts from a workplace computer: Forty-five percent of those surveyed use webmail at work; 74 percent say there is no stated policy that forbids it.

3. Losing a portable data-bearing device: Thirty-nine percent of respondents say they have lost or misplaced such a device, and 72 percent of them did not report the lost device immediately.

4. Downloading personal software onto a company computer: Sixty percent of respondents say there is no stated policy that forbids downloading personal software, a practice that 45 percent of respondents admit to.

5. Sending workplace documents as an attachment in e-mail: Thirty-three percent of respondents send work documents as attachments, and 48 percent aren’t even sure whether or not that violates policy.

6. Disabling security and firewall settings: Eighty percent of those surveyed don’t know whether disabling security is against policy; 17 percent of respondents do it.

7. Sharing passwords with co-workers: Sixty-seven percent say the company’s policy forbids sharing passwords, but 46 percent of them do it anyway.


-Abhi

Security Rules Employees Like To Break

1. Copying confidential information onto a USB memory stick: Eighty-seven percent of respondents believe their company’s policy forbids it, yet 51 percent say they do it anyway.

2. Accessing web-based e-mail accounts from a workplace computer: Forty-five percent of those surveyed use webmail at work; 74 percent say there is no stated policy that forbids it.

3. Losing a portable data-bearing device: Thirty-nine percent of respondents say they have lost or misplaced such a device, and 72 percent of them did not report the lost device immediately.

4. Downloading personal software onto a company computer: Sixty percent of respondents say there is no stated policy that forbids downloading personal software, a practice that 45 percent of respondents admit to.

5. Sending workplace documents as an attachment in e-mail: Thirty-three percent of respondents send work documents as attachments, and 48 percent aren’t even sure whether or not that violates policy.

6. Disabling security and firewall settings: Eighty percent of those surveyed don’t know whether disabling security is against policy; 17 percent of respondents do it.

7. Sharing passwords with co-workers: Sixty-seven percent say the company’s policy forbids sharing passwords, but 46 percent of them do it anyway.


-Abhi

Security Rules Employees Like To Break

1. Copying confidential information onto a USB memory stick: Eighty-seven percent of respondents believe their company’s policy forbids it, yet 51 percent say they do it anyway.

2. Accessing web-based e-mail accounts from a workplace computer: Forty-five percent of those surveyed use webmail at work; 74 percent say there is no stated policy that forbids it.

3. Losing a portable data-bearing device: Thirty-nine percent of respondents say they have lost or misplaced such a device, and 72 percent of them did not report the lost device immediately.

4. Downloading personal software onto a company computer: Sixty percent of respondents say there is no stated policy that forbids downloading personal software, a practice that 45 percent of respondents admit to.

5. Sending workplace documents as an attachment in e-mail: Thirty-three percent of respondents send work documents as attachments, and 48 percent aren’t even sure whether or not that violates policy.

6. Disabling security and firewall settings: Eighty percent of those surveyed don’t know whether disabling security is against policy; 17 percent of respondents do it.

7. Sharing passwords with co-workers: Sixty-seven percent say the company’s policy forbids sharing passwords, but 46 percent of them do it anyway.


-Abhi

Security Rules Employees Like To Break

1. Copying confidential information onto a USB memory stick: Eighty-seven percent of respondents believe their company’s policy forbids it, yet 51 percent say they do it anyway.

2. Accessing web-based e-mail accounts from a workplace computer: Forty-five percent of those surveyed use webmail at work; 74 percent say there is no stated policy that forbids it.

3. Losing a portable data-bearing device: Thirty-nine percent of respondents say they have lost or misplaced such a device, and 72 percent of them did not report the lost device immediately.

4. Downloading personal software onto a company computer: Sixty percent of respondents say there is no stated policy that forbids downloading personal software, a practice that 45 percent of respondents admit to.

5. Sending workplace documents as an attachment in e-mail: Thirty-three percent of respondents send work documents as attachments, and 48 percent aren’t even sure whether or not that violates policy.

6. Disabling security and firewall settings: Eighty percent of those surveyed don’t know whether disabling security is against policy; 17 percent of respondents do it.

7. Sharing passwords with co-workers: Sixty-seven percent say the company’s policy forbids sharing passwords, but 46 percent of them do it anyway.


-Abhi

Security Rules Employees Like To Break

1. Copying confidential information onto a USB memory stick: Eighty-seven percent of respondents believe their company’s policy forbids it, yet 51 percent say they do it anyway.

2. Accessing web-based e-mail accounts from a workplace computer: Forty-five percent of those surveyed use webmail at work; 74 percent say there is no stated policy that forbids it.

3. Losing a portable data-bearing device: Thirty-nine percent of respondents say they have lost or misplaced such a device, and 72 percent of them did not report the lost device immediately.

4. Downloading personal software onto a company computer: Sixty percent of respondents say there is no stated policy that forbids downloading personal software, a practice that 45 percent of respondents admit to.

5. Sending workplace documents as an attachment in e-mail: Thirty-three percent of respondents send work documents as attachments, and 48 percent aren’t even sure whether or not that violates policy.

6. Disabling security and firewall settings: Eighty percent of those surveyed don’t know whether disabling security is against policy; 17 percent of respondents do it.

7. Sharing passwords with co-workers: Sixty-seven percent say the company’s policy forbids sharing passwords, but 46 percent of them do it anyway.


-Abhi

Security Rules Employees Like To Break

1. Copying confidential information onto a USB memory stick: Eighty-seven percent of respondents believe their company’s policy forbids it, yet 51 percent say they do it anyway.

2. Accessing web-based e-mail accounts from a workplace computer: Forty-five percent of those surveyed use webmail at work; 74 percent say there is no stated policy that forbids it.

3. Losing a portable data-bearing device: Thirty-nine percent of respondents say they have lost or misplaced such a device, and 72 percent of them did not report the lost device immediately.

4. Downloading personal software onto a company computer: Sixty percent of respondents say there is no stated policy that forbids downloading personal software, a practice that 45 percent of respondents admit to.

5. Sending workplace documents as an attachment in e-mail: Thirty-three percent of respondents send work documents as attachments, and 48 percent aren’t even sure whether or not that violates policy.

6. Disabling security and firewall settings: Eighty percent of those surveyed don’t know whether disabling security is against policy; 17 percent of respondents do it.

7. Sharing passwords with co-workers: Sixty-seven percent say the company’s policy forbids sharing passwords, but 46 percent of them do it anyway.


-Abhi

Security Rules Employees Like To Break

1. Copying confidential information onto a USB memory stick: Eighty-seven percent of respondents believe their company’s policy forbids it, yet 51 percent say they do it anyway.

2. Accessing web-based e-mail accounts from a workplace computer: Forty-five percent of those surveyed use webmail at work; 74 percent say there is no stated policy that forbids it.

3. Losing a portable data-bearing device: Thirty-nine percent of respondents say they have lost or misplaced such a device, and 72 percent of them did not report the lost device immediately.

4. Downloading personal software onto a company computer: Sixty percent of respondents say there is no stated policy that forbids downloading personal software, a practice that 45 percent of respondents admit to.

5. Sending workplace documents as an attachment in e-mail: Thirty-three percent of respondents send work documents as attachments, and 48 percent aren’t even sure whether or not that violates policy.

6. Disabling security and firewall settings: Eighty percent of those surveyed don’t know whether disabling security is against policy; 17 percent of respondents do it.

7. Sharing passwords with co-workers: Sixty-seven percent say the company’s policy forbids sharing passwords, but 46 percent of them do it anyway.


-Abhi

Security Rules Employees Like To Break

1. Copying confidential information onto a USB memory stick: Eighty-seven percent of respondents believe their company’s policy forbids it, yet 51 percent say they do it anyway.

2. Accessing web-based e-mail accounts from a workplace computer: Forty-five percent of those surveyed use webmail at work; 74 percent say there is no stated policy that forbids it.

3. Losing a portable data-bearing device: Thirty-nine percent of respondents say they have lost or misplaced such a device, and 72 percent of them did not report the lost device immediately.

4. Downloading personal software onto a company computer: Sixty percent of respondents say there is no stated policy that forbids downloading personal software, a practice that 45 percent of respondents admit to.

5. Sending workplace documents as an attachment in e-mail: Thirty-three percent of respondents send work documents as attachments, and 48 percent aren’t even sure whether or not that violates policy.

6. Disabling security and firewall settings: Eighty percent of those surveyed don’t know whether disabling security is against policy; 17 percent of respondents do it.

7. Sharing passwords with co-workers: Sixty-seven percent say the company’s policy forbids sharing passwords, but 46 percent of them do it anyway.


-Abhi

Security Rules Employees Like To Break

1. Copying confidential information onto a USB memory stick: Eighty-seven percent of respondents believe their company’s policy forbids it, yet 51 percent say they do it anyway.

2. Accessing web-based e-mail accounts from a workplace computer: Forty-five percent of those surveyed use webmail at work; 74 percent say there is no stated policy that forbids it.

3. Losing a portable data-bearing device: Thirty-nine percent of respondents say they have lost or misplaced such a device, and 72 percent of them did not report the lost device immediately.

4. Downloading personal software onto a company computer: Sixty percent of respondents say there is no stated policy that forbids downloading personal software, a practice that 45 percent of respondents admit to.

5. Sending workplace documents as an attachment in e-mail: Thirty-three percent of respondents send work documents as attachments, and 48 percent aren’t even sure whether or not that violates policy.

6. Disabling security and firewall settings: Eighty percent of those surveyed don’t know whether disabling security is against policy; 17 percent of respondents do it.

7. Sharing passwords with co-workers: Sixty-seven percent say the company’s policy forbids sharing passwords, but 46 percent of them do it anyway.


-Abhi

Security Rules Employees Like To Break

1. Copying confidential information onto a USB memory stick: Eighty-seven percent of respondents believe their company’s policy forbids it, yet 51 percent say they do it anyway.

2. Accessing web-based e-mail accounts from a workplace computer: Forty-five percent of those surveyed use webmail at work; 74 percent say there is no stated policy that forbids it.

3. Losing a portable data-bearing device: Thirty-nine percent of respondents say they have lost or misplaced such a device, and 72 percent of them did not report the lost device immediately.

4. Downloading personal software onto a company computer: Sixty percent of respondents say there is no stated policy that forbids downloading personal software, a practice that 45 percent of respondents admit to.

5. Sending workplace documents as an attachment in e-mail: Thirty-three percent of respondents send work documents as attachments, and 48 percent aren’t even sure whether or not that violates policy.

6. Disabling security and firewall settings: Eighty percent of those surveyed don’t know whether disabling security is against policy; 17 percent of respondents do it.

7. Sharing passwords with co-workers: Sixty-seven percent say the company’s policy forbids sharing passwords, but 46 percent of them do it anyway.


-Abhi