Search

Infosec and Corporate Blogging

0 views

Zeltzer and Villafranco have probably the most coherent list of Do's and Don'ts when it comes to corporate blogging out there, its an absolute must read.

The Law.com When doing a Google search on companies to see what intellectual property has been exposed, and how to do some form of recovery and damage control. I usually run into company sponsored or company employees saying how great the company is, and how wonderful and life fulfilling those products are. The problem is when you get into the comments section of the file, and see that not everyone agrees with the wonderfulness of the product. The blog writer is then usually put into a position to support/defend their entry, and many times the language degenerates into finger pointing pain.

Alternatively, even better, it is a one off blog entry somewhere, with many negative comments, but no response from the original blog writer to support their statement or their position. All that ends up in Google, meaning when searching for the company, the negative comments are seen, and people have a way of getting their point across. A well-maintained blog entry usually has both positive and negative comments, or all negative or all positive depending on how the blog comments are being shaped by the blog writer. (Blog writers do shape their comments, when they have access to approve or disapprove of the comments being posted).

The other very important Don't

DON'T terminate employees for posting inappropriate content to corporate blogs without considering the risk of wrongful termination claims, especially where the company does not have a consistent practice on how it treats employees who post content online. Employees may claim that the employer authorized the posting, and is now discriminating against them for exercising their right to organize. Source: The Law This is very important as a "do" because even if the blog is not directly associated with the company, if a person can prove that the person worked for the company, and wrote negative articles about people in the company, outside the company, where the claims can not be proved (or a person had a private identity), this can open up not only the blogger to liability, but the corporation that sponsored the blog as well. Corporate sponsorship of blogs can be tricky at best, and having an employee that is disparaging of co-workers, can not stay on script as to what the blog is about, or otherwise becomes a huge management issue. As well it can become an information security issue in the longer run if trade secrets or internal information is posted to the web site.

Companies should read the Do's and Don'ts from the Law.com, its coherent and applicable to how to manage and develop good policy around corporate sponsored blogs.
' /> Del.icio.us</a> | <a href=' /> Digg</a> | <a href=' />Reddit</a> | <a href=' /> Furl</a>
<br />
<br />
Bookmark Murdok: <a href=' /></a>                </div>
                
                <script>
                (function() {
                    function initCopyableSections() {
                        document.querySelectorAll('.article-content .copyable-section').forEach(function(section) {
                            if (section.querySelector('.copyable-section__btn')) return;
                            var btn = document.createElement('button');
                            btn.type = 'button';
                            btn.className = 'copyable-section__btn';
                            btn.setAttribute('aria-label', 'Copy to clipboard');
                            var label = section.getAttribute('data-copy-label');
                            btn.textContent = label ? 'Copy ' + label : 'Copy';
                            section.appendChild(btn);
                            btn.addEventListener('click', function() {
                                var contentEl = section.querySelector('.copyable-section__content');
                                var text;
                                if (contentEl) {
                                    text = contentEl.textContent.trim();
                                } else {
                                    var clone = section.cloneNode(true);
                                    var btnClone = clone.querySelector('.copyable-section__btn');
                                    if (btnClone) btnClone.parentNode.removeChild(btnClone);
                                    text = clone.textContent.trim();
                                }
                                if (!text) return;
                                navigator.clipboard.writeText(text).then(function() {
                                    var t = btn.textContent;
                                    btn.textContent = 'Copied!';
                                    btn.classList.add('copied');
                                    setTimeout(function() {
                                        btn.textContent = t;
                                        btn.classList.remove('copied');
                                    }, 2000);
                                });
                            });
                        });
                    }
                    if (document.readyState === 'loading') {
                        document.addEventListener('DOMContentLoaded', initCopyableSections);
                    } else {
                        initCopyableSections();
                    }
                })();
                </script>
                
                <!-- Tags -->
                                
                <!-- Correction Form -->
                <div class=

Suggest a Correction

Found an error or have a suggestion? Let us know and we'll review it.

Share this article

Comments (0)

Please sign in to leave a comment.

No comments yet. Be the first to comment!