[ Upcoming Event] Mobile Security Summit 2016 – South Africa

•April 1, 2016 • Leave a Comment

Rhys Mossom will be providing an indepth, out of the box look at what mobile security means and the importance of well-organized collaboration.

The two day event will take place at Indaba Hotel in Johannesburg on 11 &
12 May 2016.

It is possible to download a program from:

Mobile Security Summit 2016 Brochure Download

The programme will cover a range of current topics which are pertinent to
mobile security. The content includes subject matter on the rise of mobile
malware, creating secure mobile usage policies, ensuring safe mobile
payments, biometric integration, data analytics and the impact mobile has
upon organisations.
Modern organisations need to be up to date and creative towards their
security approach due to the broad nature of evolving threats in the mobile
realm. The expert speaker panel will share their wealth of experience in
mobile security by discussing the latest innovations in keeping the mobile
channel secure.
The event will bring professionals from across the mobile sphere together.
The content from the programme topics is beneficial to banks, IT firms,
security solutions, telecommunication companies, service providers and
software developers.
For more information contact Project Manager, Jesse de Bruyn

Topics to be addressed
• Securing end to end experiences in a mobile-first cloud-first world
• Mobile security threats
• Establishing solutions to counteract evolving mobile threats
• Understanding risk and threats as they apply to mobile application security
• From where to where?
• Radio frequency signals: sniffing, jamming and exploitation
• Closing the mobile security gap
• Growing mobile security within the organisation
• The dark web and cyber-crime mechanics
• Mobile malware terror
• Integration of data and biometrics to keep the mobile channel secure


SNMP: Part 1 SNMP Client in C and Introduction

•March 6, 2015 • Leave a Comment

SNMP Client written in C, started up and ready to fire!:

In this first of a two post article will cover:
-Basics of SNMP.
-Writing an SNMP Client in C.
-The usefulness it can have in conducting penetration testing and hacking.
In Part 2 I will cover
-Possible malicious use of SNMP, that could be performed by an attacker, and how this could be mitigated.

As a note, all of this is performed on a windows 7 system with Visual Studio 2013 as my IDE.

The SNMP protocol is used for communicating with network devices.

Typical queries in SNMP are things such as: bytes In/Out on an interface, errors, CPU load, Uptime, and temperature.
SNMP requests are performed through a numbering scheme where each perion (.) represents a leg of the MIB tree pictured below. The numbers represent the member of that MIB tree leg extention:



As pictured above it is easy to see that an SNMP request such as a GET or a SET request with the data of represents the SysDescr member.
Or expanded, it represents: iso->org->dod->Internet->directory->mib-2->SysDescr.

SNMP is generally defined under the following RFC’s, and is carried out under UDP communication and on port 161 and 162.

Version 1 was originally written in 1988.
Version 1:RFC1155, RFC1156, RFC1157
Version 2:RFC1901, RFC1908, RFC2578
These updates Extended version 1, added new data types, and added better retrieval methods such as GETBULK.
version 3:RFC3411, RFC3418 (w/security)

Typically SNMPv2 (v2c) is used.

Basic commands in SNMP are:
GET (client to server), Query for a value.
GET-NEXT (client -> server), Get next value (list of values for a table)
GET-RESPONSE (server to client), Response to GET/SET, or error.
SET (client to server), Set a value, or perform action.
TRAP (server to client), Spontaneous notification from equipment (line down,temperature above threshold, etc).

Community strings act to only allow “authorized” requests.
The common (and misfortune) practice of leaving things default leads to the widespread use of the two default community names, although others exists, and can be used to find some really interesting equipment.
The two default (or one of the 3 variations used for each “public” and “private”) common community strings are “public”, “Public”, “PUBLIC” and “private”, “Private”, “PRIVATE”.
Public is for read-only access to the device.
Private is used for write access to the device..

Below is a GET request in Wireshare and the subsequent server response:


Wireshark response to GET request:
snmp-packet received

Version 1, originally conceived in the 80’s. Community strings are sent in plain text.
Version 2c: SNMP v2c was developed to fix some of the problems in v1. Community strings are still sent in plain-text.
Version 3: The newest version of SNMP, v3 supports full security and authentication.

Refer to the RFCs quoted above for more information.



Below is some source code that performs a query with a GET-NEXT request, and subsequently walks the table by successively requesting the OID string returned in each request, starting with “1.3”.
The compiled Executable and accompanying project file is also downloadable.

[ ZIP ] VS2013 Project
[ ZIP ] Executable
[ C   ] C Code for SNMP Client.

Happy 2015

•January 4, 2015 • Leave a Comment


My moms art work!

•December 9, 2014 • Leave a Comment

Nicola Holgate Artist Painting

My mothers art work. She works with a variety of artistic mediums.

For more have a look at Nicola Holgates webpage:

Homepage: http://www.nicolaholgate.com

She is available for contact at:



Telephone number: +267 393 0645
Mobile number: +267 726 36 016

Market Research Survey

•December 5, 2014 • Leave a Comment
 Rhys A. Mossom Network Security Services

Market Research Survey for Rhys A. Mossom Network Security Services

Hi Guys, please take a moment to take this survey of ours. Every result is appreciated. We are using it as part of our market-research.

Kind Regards,
Rhys A. Mossom


home page:

MS-DOS – Trip Down Memory Lane…

•November 2, 2014 • Leave a Comment

Version 2.1 and Version 5.0:


and for interests sake platters out of some old hard-drives. (vernier caliper is showing 3.5inches):


Rhys A. Mossom Network Security Services

•October 25, 2014 • Leave a Comment

Rhys A. Mossom Network Security Services

[ Company Website ] R.A.M. Network Security Services Website

[ Company Twitter ] R.A.M. Network Security Services Twitter

[ Company LinkedIn ] R.A.M. Network Security Services LinkedIn

[ Company Facebook ] R.A.M. Network Security Services Facebook

Rhys A. Mossom Network Security Services has been formed to offer Cyber Security offerings to South Africa, Southern Africa and on a wider international scale.

Rhys A. Mossom Network Security Services is based in Johannesburg, South Africa delivering international services, specializing in ethical hacking, penetration testing, web-application testing, vulnerability assessments, and information-security compliance assessments.

R.A.M Network Security Services encompasses a broad range of security-testing methods known as Ethical Hacking. It is the practice of assessing the security posture of a given security system, using the same tools and techniques employed by blackhat-hackers on a daily basis. These techniques can be performed against system Operating Systems, services, software and website-applications. There are a number of ways to achieve various results, according to your business needs.

The benefits of a comprehensive analysis can range from reducing the likely hood of downtime and financial or other business implications and damage to electronic assets.

According to the currently available statistics at the time of writing, the document “Net Losses: Estimating the Global Cost of Cybercrime Economic impact of cybercrime II Center for Strategic and international Studies – June 2014” by the renowned global Security company, McAffee, estimates that 0.14% of South Africa’s GPD is lost through cyber-crime. This equates to just less than five (R4.91 Billion) Billion Rand that is stolen. Additionally South Africa ranks number six amongst the most targeted counties for cyber-crime globally by the U.S. Federal Bureau of Investigation (FBI), whilst another renowned security company, Symantec, listed South Africa as the third worst hit country globally by cyber-crime.