DCS 04 LabManual
DCS 04 LabManual
BLOCK
4 LABORATORY MANUAL
Course Writer
Every BIG-IP system has an account named root. A user who logs in to
the system using the root account has full access to all BIG-IP system
resources, including all administrative partitions and command line
interfaces.
Every BIG-IP system has an account named admin. A user who logs in
to the system using the admin account has the Administrator role, which
grants the user full access to all BIG-IP system resources, including all
administrative partitions on the system. By default, the admin user
account has access to the BIG-IP Configuration utility only. However,
users logged in with this account can grant themselves access to
Local accounts
A BIG-IP user with the correct user role can create other local user
accounts for BIG-IP system administration. Each local user account on
the BIG-IP system has one or more user roles assigned to the account
(one per partition), as well as permissions related to tmsh and Bash shell
access.
Remote accounts
Note: You are not required to have any user accounts on the BIG-IP system
other than the root and admin accounts. However, F5 Networks
recommends that you create other user accounts, as a way to intelligently
control administrator access to system resources.
If you have an Administrator user role, you can use the BIG-IP
Configuration utility to change the passwords of
the root and admin accounts.
3. Make a new user account or if the existing one is yours then skip
this step.
7. Confirm Password
8. Click on OK.
If you’ve got a Word document that you don’t want prying eyes to see or
modify, you’ll want to lock down your file with a strong password. Word
comes with password protection capabilities built-in to every version.
Follow this guide to protect any document in any version of Word, for both
Windows and Mac OS X.
1. Click the "File" in the upper-left corner. If the Info tab doesn’t
automatically open, click the Info tab.
In order for the password to take effect, you must save the file.
1. Move your mouse over Prepare. This option is located between Print
and Send. A new menu will appear.
In order for the password to take effect, you must save the file.
3. Remove your password. If you want to remove your password, open the
document and click the Microsoft Office Button again. Hover over Prepare
and select “Encrypt Document”. There will be a password in the box, delete
it and press OK.
1. Click the Tools menu. Click Options and a new window will open.
Click on the Security tab.
2. Create a password. In the Security tab, enter your new password in the
“Password to open” field. Press OK to save the password. You will not
be able to retrieve this password if you forget it, so write it down in a
safe location.
1. Click the Word menu. This is located in the top-left corner, between
the Apple menu and the File menu. Select Preferences.
In order for the password to take effect, you must save the file.
Aim: To study the steps to remove Passwords from Microsoft Word 2007.
3.1 Introduction
Microsoft Word 2007 can be useful for personal and business applications.
You can create letters, flyers, mailing labels, greeting cards and documents
of numerous types quickly and easily. Word 2007 also allows you to create
passwords for opening and for editing your documents. There are occasions
where you may need to remove those passwords, however, and that can be
challenging if you don't know how. See Step 1 below for more information
on how to remove passwords from Microsoft Word 2007 without destroying
the text of the document in question.
Step 1
Step 3
You may need to recreate the file if you have forgotten your password.
4.1 Introduction
You don’t have to go far to find out how important database security is. For
instance, Target is still reeling from their systems being hacked, exposing
the credit card information of many of their customers. It’s the kind of harm
that requires a lot of time, money, and resources for damage control, as well
as the aftermath of breaking the trust in the company and diverting resources
toward making sure it doesn’t happen again.
Here are five things you can do to keep your company and customer
information safe and secure.
You can try to make a combination of letters, numbers and symbols to throw
off would-be hackers. You can check your password here to see how long it
One other suggestion is to set rules that make employees change passwords
on a revolving basis. If a password isn’t changed after 90 days, lock out that
account pending administrator approval to make sure that an old password
isn’t a hacker’s way in.
It is a simple way to protect your database. Leave it out of sight. This means
keeping it hidden from search engine results through the robots.txt file, and
also not linking to it directly. While you want employees to have access to
database information, you may not want to put the log-in directly on the site.
If you have an online database, do yourself a favour and keep it on a need-
to-know basis. After all, the first step toward hacking a database is finding it
in the first place.
For instance, you might want to have users, super users, administrators, and
super administrators. Users can access or input basic information, but not
alter information beyond what they’ve put in, whereas a superuser has
computer permissions that allow wider access to data without being able to
change everything. An administrator can work above all of these users,
altering the structure of the database or having access to more sensitive
information, while a super administrator can run the whole operation. For
the upper tiers, you’ll want to keep the number of people with those
Services
Services are prime vulnerability points for attackers who can exploit
the privileges and capabilities of the service to access the server and
potentially other computers. Some services are designed to run with
privileged accounts. If these services are compromised, the attacker
can perform privileged operations. By default, database servers
generally do not need all services enabled. By disabling unnecessary
and unused services, you quickly and easily reduce the attack
surface area.
Protocols
Limit the range of protocols that client computers can use to connect
to the database server and make sure you can secure those protocols.
Accounts
Ports
Unused ports are closed at the firewall, but it is required that servers
behind the firewall also block or restrict ports based on their usage.
For a dedicated SQL Server, block all ports except for the necessary
SQL Server port and the ports required for authentication.
Registry
Basics
Use at least eight characters, the more characters the better really, but
most people will find anything more than about 15 characters difficult
to remember.
Use a random mixture of characters, upper and lower case, numbers,
punctuation, spaces and symbols.
Don't use a word found in a dictionary, English or foreign.
Never use the same password twice.
Things to avoid
Don't just add a single digit or symbol before or after a word. e.g.
"apple1"
Don't double up a single word. e.g. "appleapple"
Don't simply reverse a word. e.g. "elppa"
Don't just remove the vowels. e.g. "ppl"
Key sequences that can easily be repeated. e.g. "qwerty","asdf" etc.
Don't just garble letters, e.g. converting e to 3, L or i to 1, o to 0. as in
"z3r0-10v3"
Bad Passwords
Choosing a password
Use a secure password manager, see the downloads page for a list of a
few that won't cost you anything.
Use a text file encrypted with a strong encryption utility.
Choose passwords that you find easier to remember.
Bad Examples
Good Examples
None of these good examples are actually good passwords, that's because
they've been published here and everybody knows them now, always choose
your own password don't just use somebody elses.
Brute force attack– This method is similar to the dictionary attack. Brute
force attacks use algorithms that combine alpha-numeric characters and
symbols to come up with passwords for the attack. For example, a password
of the value “password” can also be tried as p@$$word using the brute force
attack.
6.1 Introduction
Primarily, hacking was used in the "good old days" for leaking information
about systems and IT in general. In recent years, thanks to a few villain
actors, hacking has taken on dark connotations. Conversely, many
corporations employ hackers to test the strengths and weaknesses of their
own systems. These hackers know when to stop, and the positive trust they
build earns them a large salary.
If you're ready to dive in and learn the art, this article will share a few tips to
help you get started!
1. Use a *nix terminal for commands. Cygwin will help emulate a *nix
for Windows users. Nmap in particular uses WinPCap to run on
Windows and does not require Cygwin. However, Nmap works poorly
on Windows systems due to a lack of raw sockets. You should also
consider using Linux or BSD, which are both more flexible. Most Linux
distributions come with many useful tools pre-installed.
2. Secure your machine first. Make sure you've fully understood all
common techniques to protect yourself. Start with the basics — but
make sure you have authorization to attack your target: attack your own
network, ask for written permission, or set up your own laboratory with
virtual machines. Attacking a system, no matter its content, is illegal and
WILL get you in trouble.
4. Determine the operating system (OS). Run a scan of the ports, and try
pOf, or nmap to run a port scan. This will show you the ports that are
open on the machine, the OS, and can even tell you what type of firewall
or router they are using so you can plan a course of action. You can
activate OS detection in nmap by using the -O switch.
Try other TCP and UDP ports that may have been forgotten, such as
Telnet and various UDP ports left open for LAN gaming.
An open port 22 is usually evidence of an SSH (secure shell) service
running on the target, which can sometimes be brute forced.
8. Use various tricks. Often, to gain super-user status you have to use
tactics such as creating a buffer overflow, which causes the memory to
dump and that allows you to inject a code or perform a task at a higher
level than you're normally authorized.
In Unix-like systems this will happen if the bugged software has setuid
bit set, so the program will be executed as a different user (super-user
for example).
Only by writing or finding an insecure program that you can execute
on their machine will allow you to do this.
10. Cover your tracks. Don't let the administrator know that the system is
compromised. Don't change the website (if any), and don't create more
files than you really need. Do not create any additional users. Act as
quickly as possible. If you patched a server like SSHD, make sure it has
your secret password hard-coded. If someone tries to login with this
password, the server should let them in, but shouldn't contain any crucial
information.
References:
1. http://www.wikihow.com
2. https://www.wikipedia.org