Sharp Angle Close – When the customer asks for a concession, whether it is price, delivery or additional features, respond by asking, “If I can do that for you today, will you sign a purchase order?” This is an important closing question – if you agree without asking for close, then the customer has an open door to continue asking for concessions.
The Art of saying something without saying anything -This is a great capability for under performing sales people in joint internal meetings or end of quarter business reviews, otherwise knowns as QBRs. Its when a Sales Directors ask a Sales Rep about performance and how they will make sure to hit targets next quarter. Its a skill of answering that questions but not answering the question. I am not sure how to do this, but i seen it happen and then the Sales Director say Good job Mr X and move on the the next Sales Guy. This is a very amazing skill and astonishing to experience live.
Rehost, i.e. redeploy applications to a different hardware environment and change the application’s infrastructure configuration. Rehosting an application without making changes to its architecture can provide a fast cloud migration solution. However, the primary advantage of IaaS, that – teams can migrate systems quickly, without modifying their architecture – can be its primary disadvantage as benefits from the cloud characteristics of the infrastructure, such as scalability, will be missed.
Refactor, i.e. run applications on a cloud provider’s infrastructure. The primary advantage is blending familiarity with innovation as “backward-compatible” PaaS means developers can reuse languages, frameworks, and containers they have invested in, thus leveraging code the organization considers strategic. Disadvantages include missing capabilities, transitive risk, and framework lock-in. At this early stage in the PaaS market, some of the capabilities developers depend on with existing platforms can be missing from PaaS offerings.
Revise, i.e. modify or extend the existing code base to support legacy modernization requirements, then use rehost or refactor options to deploy to cloud. This option allows organizations to optimize the application to leverage the cloud characteristics of providers’ infrastructure. The downside is that kicking off a (possibly major) development project will require upfront expenses to mobilize a development team. Depending on the scale of the revision, revise is the option likely to take most time to deliver its capabilities.
Rebuild, i.e. Rebuild the solution on PaaS, discard code for an existing application and re-architect the application. Although rebuilding requires losing the familiarity of existing code and frameworks, the advantage of rebuilding an application is access to innovative features in the provider’s platform. They improve developer productivity, such as tools that allow application templates and data models to be customized, metadata-driven engines, and communities that supply pre-built components. However, lock-in is the primary disadvantage so if the provider makes a pricing or technical change that the consumer cannot accept, breaches service level agreements (SLAs), or fails, the consumer is forced to switch, potentially abandoning some or all of its application assets.
Replace, i.e. discard an existing application (or set of applications) and use commercial software delivered as a service. This option avoids investment in mobilizing a development team when requirements for a business function change quickly. Disadvantages can include inconsistent data semantics, data access issues, and vendor lock-in.
You will need to document all your activities, from meeting minutes and decisions down to commands typed into your systems by your incident response team.
For each step, you will need to record, at minimum:
Get your incident response team together! Where possible use phone communication – your email and chat systems may be compromised and you might tip off an attacker that you are aware of them.
You’ll need a broad set of people:
Remember! Apply a need-to-know policy for now – no need to blow it out of proportion just yet.
Hint: If you have Cyber Insurance, notify them of a potential claim.
Working with your team, determine as best you can what devices have been compromised.
Assume the worst – that more of your environment is compromised. Yes, it will increase the scope of the response, but will reduce the chance of an incident recurring.
‘Indicators of compromise’ are unexpected or suspicious behaviour which may mean an incident has occurred. This may include behaviours such as:
A hacker will try to traverse to other systems, so isolate affected systems as soon as possible. The goal here is to prevent the problem from getting worse.
There are some key actions – these may affect incident response, forensic, and legal activities, so make sure you do it right:
You want to keep copies of the affected system for forensic purposes.
The best approach is to remove the affected system from the environment, and provide a new system for the user, or build a new server from a clean SOE.
Of course, sometimes this isn’t possible, in which case you should:
Hint: Use the ‘dcfldd’ tool, which is available for Unix and Windows.
3rd party forensic investigators will have disk cloning hardware to perform this task if you don’t have the relevant expertise.
Eradication means removing the problem from affected systems determined through your scoping efforts.
The actual technical actions for eradication may vary considerably.
For attacks on vulnerable systems, cleaning the system and patching the system may be sufficient.
It can be very difficult and time-consuming to verify that systems are in fact secure, and malware has been completely removed. Rootkits in particular need specialist skills to detect.
We recommend rebuilding systems affected by malware, by either:
See the eradication tools in the Links below.
If you have indeed been breached, it will be best to apply further controls to ensure you are better able to prevent and detect malicious activity next time.
These controls may include:
Once you’ve eradicated the problem, you can recover the affected systems and return them to production.
Remember to check the integrity of your backups before restoring from them. Malware may have been backed up with your system and data files.
There are key actions when you recover your systems:
You need to conduct logging and monitoring of systems and network traffic to verify that the system or environment has been remediated.
If you’re satisfied that the attack has been completely eradicated, then you can formally terminate the incident and conduct post-incident activities.
Have a look at our Incident Response Guide (available to subscribers) for supporting information on conducting post-incident activities, and preparing for the next security incident.