An internal company wiki isn’t just a convenience — it qualifies and quantifies information that could easily become “institutionalized knowledge.” Your internal company wiki must embrace the philosophy that no note is too trivial.
Your internal wiki is vital, and it must be concise, easily accessible, and frequently updated. Wikis are one of the best remote tools your company can use to increase communication and productivity.
The following eight features can transform your internal company wiki from “forgotten project” into “everyday resource” and not only shorten your training time but also help prevent employees from getting stuck during their work.
Maybe you’ve just heard the terms “intranet” and “extranet” and want to know more, or you’re an IT tech who’s asked about extranets and intranets on a daily basis and would like a learning resource to point inquisitive people to.
In either case, we’re here to help explain the difference between intranet and extranet, explain what they’re used for, and even offer some strategies for safely setting up and maintaining your own external networks.
WordPress is the most popular CMS in the world. More than 409 million viewers browse over 20 billion pages every month. On the back end, there are over 55,000 plugins available to extend and customize the platform to fit your team’s needs.
WordPress is an incredibly powerful and versatile tool for publishers; however, because it’s so ubiquitous, it’s also ripe for hackers.
How do you ensure that your WordPress website is secure? Here, we’ve listed 15 of our favorite WordPress security plugins to install to shield your site from cybercriminals.
You might already know that WordPress powers more than 30% of the web. It’s by far the most popular online publishing platform, and it hosts 70 million new posts per month.
But why is it so ubiquitous? And what makes it so powerful and instinctive for users? Here, we break down five of the key benefits of WordPress for current and potential users.
We originally published this piece in 2015. We’ve updated it with additional WordPress security advice in 2019.
Our Google Apps Login Premium and Enterprise plugins allow all users with an email address in an organization’s Google Apps domain to log in to the WordPress site with one click. If the user doesn’t have an account in WordPress already, one is automatically created based on their Google profile information — taking their first name and last name, for example. The plugin needs to generate a unique WordPress username, so the simplest thing is for the plugin to use the email address as the username directly. This ensures it is unique — but an email address can be long and cumbersome as a username when used throughout the site.
Open source WordPress powers more than 30% of the World Wide Web. Users publish over 41 million new posts on 15.5 billion pages for 409 million viewers every month.
This enormous surface area makes it a prime target for hackers. In 2018, 90% of all breached CMS sites came from WordPress according to a recent report by Sucuri.
In this post, we break down five of the most common WordPress attacks — and offer solutions to mitigate risk. (more…)
Following a series of Google Apps login phishing attacks (specifically on Google Docs) in 2017, Google made several improvements. At the time, while we welcomed Google taking steps to address the phishing problems, it caused issues for WordPress plugins.
Specifically, the updates made it challenging in cases where customer installation required individuals to create a Google Cloud project with their own OAuth 2.0 Client IDs.
To make things easier and safer for legitimate users who need to create Google applications, we recommended that Google:
- Allow users to authenticate against an OAuth ID they created using the same account as the one being used to access the app.
- Allow admins to whitelist specific ID/Secrets on their domain and also allow any regular Gmail account to whitelist for their own use.
- Provide a clearer error message where unverified apps encounter ‘Invalid Scope.’
- Deliver documentation explaining the new verification processes they have rolled out.
- Offer a more robust and selective solution than joining the ‘Risky’ Group (Google already confirmed to us they are aware this cannot be a permanent solution).
Since then, we have even more suggestions for WordPress users using Google Apps login to deter attackers.
[Image via Pexels
A popular feature of Google Apps Login Enterprise version has always been the ability to specify role mapping rules – so that members of different Google Groups can have different WordPress roles assigned to them.
The only problem was that some companies didn’t have relevant Google Groups already set up (e.g., for email@example.com to contain their Marketing team) but instead had their G Suite domain arranged around different Organizational Units to control access to various G Suite features.
[Image via Pexels]
Let’s say you want better security for your WordPress site. Maybe you want your employees to always access their WordPress account by authenticating through Google (which you see as easier than requiring all users to maintain separate usernames/passwords for WordPress as well as Gmail).
You’ve also read about brute force attacks on WordPress, so hope that a Google login will guard against those. You might also have installed a plugin such as Limit Login Attempts to prevent multiple login attempts from the same IP address — likely a sign of a brute force attack (although increasingly such attacks are performed from distributed IPs).